← previous blocknext block →recent activity
Analyzing
Block #106,435,247
15 transactions · 15 stateful · 2026-09-20 10:07:34 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,435,247 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w07w18w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0debfa5…c63e
0x34b655…2a6f
12 touches
15 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0x9b7187dd…3085
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x109d8a52…a7b7
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 0xe0debfa5a1…2ac63e
Audit this contract →
← previous block·next block →recent activity