← previous blocknext block →recent activity
Analyzing
Block #106,367,199
30 transactions · 28 stateful · 2026-09-20 04:25:06 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
2.1
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,367,199 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w315w416w317w520w621w724w825w926w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde00fca6…3969
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
8 touches
6 conflicts
0x464e3025…0596
0x34b655…2a6f
8 touches
6 conflicts
0x74e46435…fdcd
0x34b655…2a6f
8 touches
6 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xde00fca6f9…a23969
Audit this contract →
← previous block·next block →recent activity