← previous blocknext block →recent activity
Analyzing
Block #101,092,163
15 transactions · 14 stateful · 2026-09-01 16:40:17 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,092,163 · 15 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
2w05w06w19w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5784baac…ac7e
0x34b655…2a6f
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x256172b1…107d
0x34b655…2a6f
2 touches
0 conflicts
0x270e5664…c0e2
0x34b655…2a6f
2 touches
0 conflicts
0x5746581b…0cb1
0x34b655…2a6f
2 touches
0 conflicts
0x685dd98e…605b
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 0x5784baac17…d4ac7e
Audit this contract →
← previous block·next block →recent activity