← previous blocknext block →recent activity
Analyzing
Block #106,383,246
22 transactions · 21 stateful · 2026-09-20 05:45:52 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,383,246 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w010w111w213w314w417w218w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0xecc4ac19…b4ac
0x34b655…2a6f
6 touches
3 conflicts
0x08137337…8610
0x34b655…2a6f
6 touches
3 conflicts
0xea2a1d1b…4115
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity