← previous blocknext block →recent activity
Analyzing
Block #106,186,225
31 transactions · 30 stateful · 2026-09-19 13:14:15 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,186,225 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w28w316w117w218w319w420w421w522w523w624w725w826w927w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
12 touches
15 conflicts
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xd6cfd0c2…991f
0x73ca90…1130
10 touches
10 conflicts
0xd6cfd0c2…991e
0x73ca90…1130
10 touches
10 conflicts
0x0033014e…086d
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity