← previous blocknext block →recent activity
Analyzing
Block #106,950,024
25 transactions · 20 stateful · 2026-09-22 05:19:31 UTC
Parallelism
72/100
Blocked
65%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,950,024 · 25 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
1w02w03w14w15w26w07w19w010w111w112w113w215w316w420w222w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f7dd39…d845
0x34b655…2a6f
10 touches
10 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0x82e501f6…e285
0x34b655…2a6f
8 touches
6 conflicts
0xc953c572…34b1
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xcc844ab5…4c6d
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
10 conflicts on slot 0xf4f7dd39bc…e6d845
Audit this contract →
← previous block·next block →recent activity