← previous blocknext block →recent activity
Analyzing
Block #106,474,346
18 transactions · 17 stateful · 2026-09-20 13:24:23 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,474,346 · 18 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
1w02w13w04w15w16w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde94a368…95d1
0x34b655…2a6f
12 touches
15 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7d5222a8…ef79
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0xa242e227…2e45
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
15 conflicts on slot 0xde94a36896…1195d1
Audit this contract →
← previous block·next block →recent activity