← previous blocknext block →recent activity
Analyzing
Block #91,544,684
8 transactions · 7 stateful · 2026-07-30 05:20:27 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,544,684 · 8 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
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe4c1abbf…26e3
0x34b655…2a6f
4 touches
1 conflict
0x5c4355bb…e317
0x34b655…2a6f
4 touches
1 conflict
0x7015836e…7340
0x34b655…2a6f
4 touches
1 conflict
0x7015836e…7341
0x34b655…2a6f
4 touches
1 conflict
0x9a9450c3…e1bf
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
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 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity