← previous blocknext block →recent activity
Analyzing
Block #106,342,403
16 transactions · 15 stateful · 2026-09-20 02:20:18 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,342,403 · 16 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
10w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9cbef147…3bd5
0x34b655…2a6f
4 touches
1 conflict
0xa139e1f5…bed2
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x63858fca…4df7
0x34b655…2a6f
3 touches
1 conflict
0x9ae4aa46…597f
0x754704…b603
2 touches
0 conflicts
0xde93ff88…37ec
0x754704…b603
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 0x9cbef147a6…843bd5
Audit this contract →
← previous block·next block →recent activity