← previous blocknext block →recent activity
Analyzing
Block #101,152,072
9 transactions · 8 stateful · 2026-09-01 21:41:39 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,152,072 · 9 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
1w02w13w05w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04795529…c98b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x52404f3d…4c2e
0x34b655…2a6f
2 touches
0 conflicts
0x58caf8db…fb06
0x34b655…2a6f
2 touches
0 conflicts
0x7ecbee7e…8033
0x34b655…2a6f
2 touches
0 conflicts
0x962713d6…7374
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 0x0479552909…f9c98b
Audit this contract →
← previous block·next block →recent activity