← previous blocknext block →recent activity
Analyzing
Block #106,474,343
14 transactions · 14 stateful · 2026-09-20 13:24:22 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,474,343 · 14 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
1w02w13w27w08w39w410w511w612w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde94a368…95d1
0x34b655…2a6f
12 touches
15 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
0xa242e227…2e45
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
0x809f2ba8…89d3
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
15 conflicts on slot 0xde94a36896…1195d1
Audit this contract →
← previous block·next block →recent activity