← previous blocknext block →recent activity
Analyzing
Block #93,199,971
9 transactions · 8 stateful · 2026-08-05 00:09:09 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,199,971 · 9 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
2w03w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3e6c02a…d3d4
0x34b655…2a6f
6 touches
3 conflicts
0xa34d8480…e07a
0x34b655…2a6f
4 touches
1 conflict
0xadfb803d…b5cb
0x34b655…2a6f
4 touches
1 conflict
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x0a07805e…94a5
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 0xe3e6c02aeb…9dd3d4
Audit this contract →
← previous block·next block →recent activity