← previous blocknext block →recent activity
Analyzing
Block #93,362,727
14 transactions · 12 stateful · 2026-08-05 13:47:27 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,362,727 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc01decc3…08a1
0x34b655…2a6f
4 touches
2 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x2a9d3054…31cf
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x3727225e…a3cf
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x7e2f09bc…dad7
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
2 conflicts on slot 0xc01decc387…5708a1
Audit this contract →
← previous block·next block →recent activity