← previous blocknext block →recent activity
Analyzing
Block #101,020,403
16 transactions · 15 stateful · 2026-09-01 10:38:55 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,020,403 · 16 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
5w06w113w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9654e93b…e153
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf9f033e6…fa47
0x34b655…2a6f
4 touches
1 conflict
0x18349fb3…7358
0x065c9d…c394
2 touches
0 conflicts
0x215fc8e5…7a18
0x065c9d…c394
2 touches
0 conflicts
0x3804ab0e…4d69
0x065c9d…c394
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 0x9654e93bbb…50e153
Audit this contract →
← previous block·next block →recent activity