← previous blocknext block →recent activity
Analyzing
Block #104,023,664
23 transactions · 21 stateful · 2026-09-11 23:14:49 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,023,664 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w211w112w115w317w218w319w421w022w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b8e717a…7114
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x61ca6437…2142
0x34b655…2a6f
8 touches
6 conflicts
0xfe1f5ba4…ee77
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x051f657c…809d
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
10 conflicts on slot 0x6b8e717a9e…667114
Audit this contract →
← previous block·next block →recent activity