← previous blocknext block →recent activity
Analyzing
Block #104,810,815
17 transactions · 17 stateful · 2026-09-14 17:48:29 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,810,815 · 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
3w04w17w28w19w210w311w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4b2a427…0234
0x34b655…2a6f
6 touches
3 conflicts
0x303d582e…aac0
0x34b655…2a6f
6 touches
3 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5c3953d6…4dcb
0x34b655…2a6f
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
3 conflicts on slot 0xf4b2a42760…660234
Audit this contract →
← previous block·next block →recent activity