← previous blocknext block →recent activity
Analyzing
Block #93,573,629
11 transactions · 9 stateful · 2026-08-06 07:27:42 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,573,629 · 11 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
1w02w03w14w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb59e680d…475d
0x34b655…2a6f
6 touches
3 conflicts
0xedf0ec10…fe02
0x34b655…2a6f
4 touches
1 conflict
0xb06a48e8…d6d1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0308
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0309
0x34b655…2a6f
4 touches
1 conflict
0xe3476918…1ef2
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
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 0xb59e680d12…10475d
Audit this contract →
← previous block·next block →recent activity