← previous blocknext block →recent activity
Analyzing
Block #106,421,315
34 transactions · 30 stateful · 2026-09-20 08:57:27 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
2.56
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,421,315 · 34 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w612w313w714w515w617w423w724w825w926w1027w1128w1229w1330w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8af7ffe…3f3c
0x34b655…2a6f
18 touches
36 conflicts
0x0df715f3…1601
0x34b655…2a6f
14 touches
21 conflicts
0x5af714ca…bb3e
0x34b655…2a6f
14 touches
21 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
14 touches
21 conflicts
0x7ed0f99d…6029
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
12 touches
15 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0xd8af7ffef3…bc3f3c
Audit this contract →
← previous block·next block →recent activity