← previous blocknext block →recent activity
Analyzing
Block #101,993,625
13 transactions · 13 stateful · 2026-09-04 20:19:38 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,993,625 · 13 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
2w03w15w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x347e3dae…4c41
0x34b655…2a6f
4 touches
1 conflict
0x767c56c7…ec85
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0e85cc8b…d506
0x34b655…2a6f
2 touches
0 conflicts
0x253fcd81…613c
0x34b655…2a6f
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 0x347e3dae67…1f4c41
Audit this contract →
← previous block·next block →recent activity