← previous blocknext block →recent activity
Analyzing
Block #91,423,460
19 transactions · 19 stateful · 2026-07-29 19:09:40 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,423,460 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w19w210w313w314w415w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
6 touches
3 conflicts
0x61b266a1…2ec4
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x87526395…a96e
0x34b655…2a6f
4 touches
1 conflict
0x8b66399b…8d29
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity