← previous blocknext block →recent activity
Analyzing
Block #93,347,451
10 transactions · 9 stateful · 2026-08-05 12:30:38 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,347,451 · 10 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
2w03w15w28w2
- 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
0xd56f5e83…f3c3
0x34b655…2a6f
6 touches
3 conflicts
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0x808129fc…f97d
0x34b655…2a6f
4 touches
1 conflict
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x97531330…c5b3
0x065c9d…c394
2 touches
0 conflicts
0xb3b6458a…b233
0x065c9d…c394
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