← previous blocknext block →recent activity
Analyzing
Block #105,600,596
29 transactions · 26 stateful · 2026-09-17 12:04:19 UTC
Parallelism
72/100
Blocked
46%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,600,596 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf496f80c…d5c8
0x34b655…2a6f
16 touches
28 conflicts
0x09020e03…31e5
0x34b655…2a6f
16 touches
28 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
10 touches
10 conflicts
0x6771eae2…7014
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x1ab4ac1a…c2ec
0x34b655…2a6f
8 touches
6 conflicts
0xad1ecaad…f0d1
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
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
28 conflicts on slot 0xf496f80c95…3ed5c8
Audit this contract →
← previous block·next block →recent activity