← previous blocknext block →recent activity
Analyzing
Block #101,062,209
30 transactions · 26 stateful · 2026-09-01 14:09:15 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,062,209 · 30 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
5w06w07w18w29w312w013w114w215w116w217w320w323w428w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x153d1e25…10ea
0x34b655…2a6f
4 touches
1 conflict
0x1e393384…1d24
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
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: 0xf5b5f7f8…a36d70
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity