← previous blocknext block →recent activity
Analyzing
Block #93,881,536
12 transactions · 12 stateful · 2026-08-07 09:15:38 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,881,536 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbeac3b7…c14b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xdb44d160…960b
0x34b655…2a6f
4 touches
1 conflict
0x8d15d872…fa53
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa01f6d1b…4adf
0x34b655…2a6f
4 touches
1 conflict
0xa4c4ff40…837b
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
6 conflicts on slot 0xbbeac3b703…d0c14b
Audit this contract →
← previous block·next block →recent activity