← previous blocknext block →recent activity
Analyzing
Block #104,193,450
20 transactions · 20 stateful · 2026-09-12 13:38:05 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,193,450 · 20 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
1w03w04w15w06w27w38w410w311w414w316w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3250389…8774
0x34b655…2a6f
12 touches
15 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
8 touches
6 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfaeefeb3…889f
0x34b655…2a6f
8 touches
6 conflicts
0xe7b9eede…2538
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 0xa325038957…7f8774
Audit this contract →
← previous block·next block →recent activity