← previous blocknext block →recent activity
Analyzing
Block #105,845,051
18 transactions · 18 stateful · 2026-09-18 08:36:08 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,845,051 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w110w011w112w113w214w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe566e4e7…af2c
0x34b655…2a6f
8 touches
6 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
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
6 conflicts on slot 0xe566e4e776…e5af2c
Audit this contract →
← previous block·next block →recent activity