← previous blocknext block →recent activity
Analyzing
Block #104,193,967
16 transactions · 15 stateful · 2026-09-12 13:40:43 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,193,967 · 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
1w02w13w14w27w39w413w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ffb5637…e5c4
0x34b655…2a6f
10 touches
10 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x261cbea7…e35d
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 0x4ffb56375c…50e5c4
Audit this contract →
← previous block·next block →recent activity