← previous blocknext block →recent activity
Analyzing
Block #105,759,797
25 transactions · 23 stateful · 2026-09-18 01:25:39 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,759,797 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w09w210w315w116w317w418w519w621w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68d72d31…6da0
0x34b655…2a6f
14 touches
21 conflicts
0xf48fa71e…bb52
0x34b655…2a6f
10 touches
10 conflicts
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x6d787177…e955
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0x9eef1610…1564
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
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
21 conflicts on slot 0x68d72d31aa…066da0
Audit this contract →
← previous block·next block →recent activity