← previous blocknext block →recent activity
Analyzing
Block #105,642,704
52 transactions · 40 stateful · 2026-09-17 15:36:19 UTC
Parallelism
75/100
Blocked
63%
Avg conflicts / tx
1.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,642,704 · 52 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w09w011w012w013w114w115w216w017w118w219w321w422w532w235w136w238w339w340w441w547w848w950w1151w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x88e92ec7…696d
0x34b655…2a6f
6 touches
3 conflicts
0xdcebb2b8…5f18
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity