← previous blocknext block →recent activity
Analyzing
Block #101,680,956
15 transactions · 13 stateful · 2026-09-03 18:02:34 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,680,956 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w311w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70f836c8…cf6d
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x041d6cf6…e9d7
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x2a2896a0…2a0a
0x34b655…2a6f
4 touches
1 conflict
0x0b3a121c…f803
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x70f836c87d…3dcf6d
Audit this contract →
← previous block·next block →recent activity