← previous blocknext block →recent activity
Analyzing
Block #101,302,162
19 transactions · 14 stateful · 2026-09-02 10:16:44 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,302,162 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w115w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c366266…77e1
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x7a8274ef…ff6d
0x34b655…2a6f
4 touches
1 conflict
0x5cba30e0…d07b
0x34b655…2a6f
4 touches
1 conflict
0xec1d6663…6042
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x33ce2799…dfd1
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 0x0c36626644…6d77e1
Audit this contract →
← previous block·next block →recent activity