← previous blocknext block →recent activity
Analyzing
Block #104,333,700
16 transactions · 15 stateful · 2026-09-13 01:29:46 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,333,700 · 16 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
1w03w15w09w210w311w312w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45de70d9…e1dc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x4e135144…4167
0x34b655…2a6f
8 touches
6 conflicts
0x91ecc9ad…0464
0x34b655…2a6f
8 touches
6 conflicts
0x9084429b…a7f8
0x34b655…2a6f
8 touches
6 conflicts
0xe92e4776…498d
0x34b655…2a6f
8 touches
6 conflicts
0x7ef4ba09…2a25
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
10 conflicts on slot 0x45de70d9be…64e1dc
Audit this contract →
← previous block·next block →recent activity