← previous blocknext block →recent activity
Analyzing
Block #106,199,042
34 transactions · 30 stateful · 2026-09-19 14:18:45 UTC
Parallelism
56/100
Blocked
67%
Avg conflicts / tx
2.71
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,199,042 · 34 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w215w316w417w118w519w621w722w823w924w1025w1126w1227w1328w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x976f380d…168b
0x34b655…2a6f
24 touches
66 conflicts
0x5717771c…45ed
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4abfb389…18f4
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
10 touches
10 conflicts
0xfbabb02d…af07
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0x976f380dca…e8168b
Audit this contract →
← previous block·next block →recent activity