← previous blocknext block →recent activity
Analyzing
Block #104,868,405
12 transactions · 12 stateful · 2026-09-14 22:39:16 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,868,405 · 12 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
1w02w13w24w05w16w27w39w410w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa09be5a…1e79
0x34b655…2a6f
10 touches
10 conflicts
0x5b220dde…f257
0x34b655…2a6f
8 touches
6 conflicts
0x4a1553d9…655d
0x34b655…2a6f
8 touches
6 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
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 0xfa09be5aaf…9b1e79
Audit this contract →
← previous block·next block →recent activity