← previous blocknext block →recent activity
Analyzing
Block #105,856,641
22 transactions · 19 stateful · 2026-09-18 09:34:29 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,856,641 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w08w19w210w311w412w513w614w721w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2016dede…a4cf
0x34b655…2a6f
16 touches
28 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x97e4c862…4419
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xb9315d69…267b
0x34b655…2a6f
8 touches
6 conflicts
0x3180cd66…aaef
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
28 conflicts on slot 0x2016dede79…4da4cf
Audit this contract →
← previous block·next block →recent activity