← previous blocknext block →recent activity
Analyzing
Block #105,841,741
24 transactions · 20 stateful · 2026-09-18 08:19:22 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,841,741 · 24 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
1w07w19w010w114w015w116w117w218w319w420w521w622w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5684aadd…8d62
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa1382963…84c6
0x34b655…2a6f
12 touches
15 conflicts
0xf8ec7381…bfbb
0x34b655…2a6f
10 touches
10 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0xa60045fb…8abb
0x065c9d…c394
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0x5684aadd69…f58d62
Audit this contract →
← previous block·next block →recent activity