← previous blocknext block →recent activity
Analyzing
Block #101,324,532
17 transactions · 14 stateful · 2026-09-02 12:09:18 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,324,532 · 17 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
1w09w113w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x79641e38…0277
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0cc4c914…333b
0x34b655…2a6f
2 touches
0 conflicts
0x1192d08f…716b
0x34b655…2a6f
2 touches
0 conflicts
0x261d80ff…22dd
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 0x336486a4ab…4220bd
Audit this contract →
← previous block·next block →recent activity