← previous blocknext block →recent activity
Analyzing
Block #106,186,054
33 transactions · 32 stateful · 2026-09-19 13:13:24 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
2.36
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,186,054 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w011w112w218w219w120w321w222w223w324w425w526w627w728w829w930w1032w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x976029c0…a4de
0x34b655…2a6f
22 touches
55 conflicts
0xd41f5136…97c6
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xfbabb02d…af07
0x34b655…2a6f
10 touches
10 conflicts
0x05e1eba1…6491
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
10 touches
10 conflicts
0x1d351a9b…f2dd
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
55 conflicts on slot 0x976029c05b…f4a4de
Audit this contract →
← previous block·next block →recent activity