← previous blocknext block →recent activity
Analyzing
Block #101,895,904
20 transactions · 18 stateful · 2026-09-04 12:03:57 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,895,904 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w117w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xc0a73ae2…2e95
0x34b655…2a6f
4 touches
1 conflict
0xd187b14b…396c
0xd32edf…ff58
3 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x262ffe69…b552
0x34b655…2a6f
2 touches
0 conflicts
0x2bd1c200…56de
0x34b655…2a6f
2 touches
0 conflicts
0x3064aa69…9b0d
0x34b655…2a6f
2 touches
0 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xaf49867962…697732
Audit this contract →
← previous block·next block →recent activity