← previous blocknext block →recent activity
Analyzing
Block #104,984,267
16 transactions · 16 stateful · 2026-09-15 08:22:16 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,984,267 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w19w210w312w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62142e5c…a946
0x34b655…2a6f
8 touches
6 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
8 touches
6 conflicts
0xa8590d68…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0x19010ca7…5505
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
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
6 conflicts on slot 0x62142e5c64…68a946
Audit this contract →
← previous block·next block →recent activity