← previous blocknext block →recent activity
Analyzing
Block #106,452,621
21 transactions · 21 stateful · 2026-09-20 11:35:04 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,452,621 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w19w010w112w113w217w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x176a8d88…fb6a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2f74f175…9285
0x34ae4d…3fc5
4 touches
1 conflict
0x2f74f175…9287
0x34ae4d…3fc5
4 touches
1 conflict
0x53e50026…6d8c
0x34ae4d…3fc5
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xf1fbcd40…9515
0x34ae4d…3fc5
4 touches
1 conflict
0x0262e1c6…52e1
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 0x176a8d88a5…e7fb6a
Audit this contract →
← previous block·next block →recent activity