← previous blocknext block →recent activity
Analyzing
Block #92,698,121
14 transactions · 12 stateful · 2026-08-03 06:02:55 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,698,121 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w111w012w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0031
0x59df86…2780
4 touches
1 conflict
0xb42fe30c…8771
0x34b655…2a6f
4 touches
1 conflict
0xc1d3a81f…a25c
0x34b655…2a6f
4 touches
1 conflict
0xc44becc2…6043
0x34b655…2a6f
4 touches
1 conflict
0xcac6d3e1…66ca
0x34b655…2a6f
4 touches
1 conflict
0xef8bfb1c…20e6
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity