← previous blocknext block →recent activity
Analyzing
Block #105,540,297
17 transactions · 15 stateful · 2026-09-17 07:00:49 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,540,297 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w09w111w012w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c98027…9fd9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5ddc4a77…765e
0x34b655…2a6f
8 touches
6 conflicts
0xf496f80c…d5c8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8d6980af…d4ce
0x34b655…2a6f
6 touches
3 conflicts
0xd587e8b9…f9f8
0x34b655…2a6f
6 touches
3 conflicts
0xcff4db4b…7052
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 0xd5c98027d8…499fd9
Audit this contract →
← previous block·next block →recent activity