← previous blocknext block →recent activity
Analyzing
Block #91,411,500
12 transactions · 12 stateful · 2026-07-29 18:09:30 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,411,500 · 12 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
1w02w14w05w16w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6b4878…d72d
0x34b655…2a6f
6 touches
3 conflicts
0x6d1b72ee…6b77
0x34b655…2a6f
6 touches
3 conflicts
0x9b6c3273…9421
0x34b655…2a6f
6 touches
3 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
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 0x6f6b4878d8…0bd72d
Audit this contract →
← previous block·next block →recent activity