← previous blocknext block →recent activity
Analyzing
Block #93,346,866
14 transactions · 12 stateful · 2026-08-05 12:27:41 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,346,866 · 14 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
1w02w15w08w19w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda7f5f6e…89cd
0x34b655…2a6f
4 touches
1 conflict
0x789cc560…944c
0x34b655…2a6f
4 touches
1 conflict
0x850def09…120b
0x34b655…2a6f
4 touches
1 conflict
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0xa6389d47…9a28
0x34b655…2a6f
4 touches
1 conflict
0xc743411d…54a8
0x34b655…2a6f
4 touches
1 conflict
0xc743411d…54a9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xda7f5f6e8c…5789cd
Audit this contract →
← previous block·next block →recent activity