← previous blocknext block →recent activity
Analyzing
Block #93,307,306
9 transactions · 9 stateful · 2026-08-05 09:08:48 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,307,306 · 9 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
1w02w03w04w15w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x080c485e…dad2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe8d8a9a2…40f3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x934b15f1…b5a9
0x851145…3f07
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
1 conflict on slot 0x080c485e23…69dad2
Audit this contract →
← previous block·next block →recent activity