← previous blocknext block →recent activity
Analyzing
Block #93,327,796
9 transactions · 9 stateful · 2026-08-05 10:51:49 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,327,796 · 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
1w02w13w25w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x981b7617…6093
0x34b655…2a6f
4 touches
1 conflict
0x055b5b38…8737
0x34b655…2a6f
2 touches
0 conflicts
0x07cd985e…a0ea
0x34b655…2a6f
2 touches
0 conflicts
0x15516aa5…fc07
0x34b655…2a6f
2 touches
0 conflicts
0x1876bf0f…ab4a
0x34b655…2a6f
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity