← previous blocknext block →recent activity
Analyzing
Block #105,683,659
21 transactions · 19 stateful · 2026-09-17 19:02:28 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,683,659 · 21 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
1w02w13w25w17w08w110w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46449565…6464
0x34b655…2a6f
10 touches
10 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0xaf9dbf3b…f9ec
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa0998a89…1f5a
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x464495653c…0a6464
Audit this contract →
← previous block·next block →recent activity