← previous blocknext block →recent activity
Analyzing
Block #106,397,214
38 transactions · 36 stateful · 2026-09-20 06:56:10 UTC
Parallelism
47/100
Blocked
69%
Avg conflicts / tx
2.97
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,397,214 · 38 txs across 20 waves · depth 20
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
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w110w615w619w723w724w825w926w1027w1128w1229w1131w1335w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1c23e9…4f81
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xed863ec8…90d8
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
45 conflicts on slot 0x5e1c23e9cd…6d4f81
Audit this contract →
← previous block·next block →recent activity