← previous blocknext block →recent activity
Analyzing
Block #105,543,129
22 transactions · 21 stateful · 2026-09-17 07:15:04 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,543,129 · 22 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
1w03w15w06w28w310w011w114w315w416w517w621w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebb3362b…41f4
0x34b655…2a6f
14 touches
21 conflicts
0x1f396cee…862f
0x34b655…2a6f
10 touches
10 conflicts
0x5ddc4a77…765e
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
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 0xebb3362bb3…b841f4
Audit this contract →
← previous block·next block →recent activity