← previous blocknext block →recent activity
Analyzing
Block #101,973,361
17 transactions · 15 stateful · 2026-09-04 18:36:46 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,973,361 · 17 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
1w02w03w15w28w312w415w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a3f40b6…e39c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x3aaea161…ffcd
0x34b655…2a6f
4 touches
1 conflict
0x4deefef3…68e4
0x34b655…2a6f
4 touches
1 conflict
0x4f125e89…7ee0
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
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 0x2a3f40b662…6ee39c
Audit this contract →
← previous block·next block →recent activity