← previous blocknext block →recent activity
Analyzing
Block #104,867,564
35 transactions · 28 stateful · 2026-09-14 22:35:02 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,867,564 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w18w19w214w216w317w421w322w426w128w529w130w231w633w534w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe2cb3b1b…6332
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdf08af9e…1985
0xa6afd3…d132
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0xa952c504…7b64
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity