← previous blocknext block →recent activity
Analyzing
Block #92,002,136
14 transactions · 14 stateful · 2026-07-31 19:41:40 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,002,136 · 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
1w02w03w17w08w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbd065252…c2c8
0x34b655…2a6f
5 touches
3 conflicts
0x28ffddbe…261b
0x34b655…2a6f
4 touches
1 conflict
0x350ee6c9…432f
0x34b655…2a6f
4 touches
1 conflict
0x56de7db5…d21d
0x34b655…2a6f
4 touches
1 conflict
0x5eeea918…8147
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 0xf324b40549…56ca30
Audit this contract →
← previous block·next block →recent activity