← previous blocknext block →recent activity
Analyzing
Block #104,166,996
23 transactions · 18 stateful · 2026-09-12 11:24:00 UTC
Parallelism
57/100
Blocked
56%
Avg conflicts / tx
1.7
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,166,996 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x4b7cfc08…b1df
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x39126904…24d8
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
36 conflicts on slot 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity