← previous blocknext block →recent activity
Analyzing
Block #92,008,473
12 transactions · 11 stateful · 2026-07-31 20:13:32 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,008,473 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb666ac1f…6bd0
0x34b655…2a6f
4 touches
1 conflict
0xf0ba1410…e53f
0x34b655…2a6f
4 touches
1 conflict
0xf7abbf86…366c
0x34b655…2a6f
4 touches
1 conflict
0x02093818…08b8
0x065c9d…c394
2 touches
0 conflicts
0xc33a84c3…732c
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity