← previous blocknext block →recent activity
Analyzing
Block #106,453,325
19 transactions · 17 stateful · 2026-09-20 11:38:37 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,453,325 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w010w111w212w114w315w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02397184…a64f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x89eaf36a…4e48
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
15 conflicts on slot 0x023971841b…3fa64f
Audit this contract →
← previous block·next block →recent activity