← previous blocknext block →recent activity
Analyzing
Block #105,850,614
24 transactions · 24 stateful · 2026-09-18 09:04:09 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,850,614 · 24 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
1w02w13w24w35w012w113w214w315w316w417w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
10 touches
10 conflicts
0x319b2d8e…2494
0x34b655…2a6f
10 touches
10 conflicts
0x831f75b4…945d
0x34b655…2a6f
10 touches
10 conflicts
0x6caf33e2…c261
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0x0efc210ee8…0e70ab
Audit this contract →
← previous block·next block →recent activity