← previous blocknext block →recent activity
Analyzing
Block #105,760,590
17 transactions · 17 stateful · 2026-09-18 01:29:38 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,760,590 · 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
2w03w06w18w29w310w411w515w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16959359…a041
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x38b5b2ce…c5bb
0x2d82ac…5fd8
4 touches
1 conflict
0x3180cd66…aaef
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
15 conflicts on slot 0x169593596d…86a041
Audit this contract →
← previous block·next block →recent activity