← previous blocknext block →recent activity
Analyzing
Block #105,843,968
26 transactions · 26 stateful · 2026-09-18 08:30:41 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,843,968 · 26 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
1w02w13w26w07w18w09w112w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
14 touches
21 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
12 touches
15 conflicts
0x6861ef35…12dd
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x784d7a94…94a2
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x4d4389b2…6e07
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity