← previous blocknext block →recent activity
Analyzing
Block #101,988,846
10 transactions · 9 stateful · 2026-09-04 19:55:22 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,988,846 · 10 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
3w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x767c56c7…ec85
0x34b655…2a6f
4 touches
1 conflict
0x2c84cfcc…351b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5cf95f25…5dd0
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0b045981…4f56
0x34b655…2a6f
4 touches
1 conflict
0x1d93668e…69b7
0x34b655…2a6f
2 touches
0 conflicts
0x23b0f222…aa59
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 0x767c56c7b2…9aec85
Audit this contract →
← previous block·next block →recent activity