← previous blocknext block →recent activity
Analyzing
Block #106,370,390
19 transactions · 19 stateful · 2026-09-20 04:41:09 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,370,390 · 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
2w03w15w09w110w211w313w014w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa384061e…9f51
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
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
15 conflicts on slot 0xa384061e1d…549f51
Audit this contract →
← previous block·next block →recent activity