← previous blocknext block →recent activity
Analyzing
Block #104,868,648
24 transactions · 24 stateful · 2026-09-14 22:40:29 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,868,648 · 24 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
3w05w07w19w010w111w212w113w215w316w417w419w420w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
12 touches
15 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
10 touches
10 conflicts
0x56fe17b8…39b1
0x34b655…2a6f
10 touches
10 conflicts
0x89106c90…1c9b
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6abf33d8…c0b4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
15 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity