← previous blocknext block →recent activity
Analyzing
Block #104,195,799
18 transactions · 17 stateful · 2026-09-12 13:50:05 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,195,799 · 18 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
1w02w13w04w15w06w19w210w011w312w414w515w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
10 touches
10 conflicts
0x2bea5ce8…3c07
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa652b48e…f543
0x34b655…2a6f
6 touches
3 conflicts
0x6e6a8155…9636
0x34b655…2a6f
6 touches
3 conflicts
0x9ddfd674…2a54
0x34b655…2a6f
6 touches
3 conflicts
0x00500a94…20d5
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity