← previous blocknext block →recent activity
Analyzing
Block #91,242,482
11 transactions · 11 stateful · 2026-07-29 03:57:46 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,242,482 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd765aea…6fda
0x34b655…2a6f
6 touches
3 conflicts
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0x3c1ab6b5…4674
0x34b655…2a6f
4 touches
1 conflict
0xb514ce62…3397
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0x446e4f62…f7b6
0x34b655…2a6f
2 touches
0 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
2 touches
0 conflicts
0x50afedcd…91cc
0x34b655…2a6f
2 touches
0 conflicts
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 0xbd765aeaec…a76fda
Audit this contract →
← previous block·next block →recent activity