← previous blocknext block →recent activity
Analyzing
Block #101,068,210
12 transactions · 12 stateful · 2026-09-01 14:39:39 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,068,210 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x6266e26a…96ee
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xde440e2e…8de4
0x34b655…2a6f
3 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0x4e804b48…ef71
0x34ae4d…3fc5
2 touches
0 conflicts
0x5a784614…c50d
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186a
0x34ae4d…3fc5
2 touches
0 conflicts
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 0x1d9867ade5…7b6d9a
Audit this contract →
← previous block·next block →recent activity