← previous blocknext block →recent activity
Analyzing
Block #106,420,460
47 transactions · 43 stateful · 2026-09-20 08:53:08 UTC
Parallelism
55/100
Blocked
70%
Avg conflicts / tx
2.98
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #106,420,460 · 47 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w611w812w927w1028w1130w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1c23e9…4f81
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc04a0335…c1aa
0x34b655…2a6f
12 touches
15 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
12 touches
15 conflicts
0x310a7246…2dcb
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x5e1c23e9cd…6d4f81
Audit this contract →
← previous block·next block →recent activity