← previous blocknext block →recent activity
Analyzing
Block #106,566,012
33 transactions · 33 stateful · 2026-09-20 21:05:44 UTC
Parallelism
76/100
Blocked
64%
Avg conflicts / tx
1.97
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,566,012 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w27w38w49w111w012w116w220w222w423w328w529w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0cdd08b…6a06
0x34b655…2a6f
16 touches
28 conflicts
0xcc8faac2…c766
0x065c9d…c394
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xe0cdd08bb5…d26a06
Audit this contract →
← previous block·next block →recent activity