← previous blocknext block →recent activity
Analyzing
Block #98,947,844
21 transactions · 20 stateful · 2026-08-25 04:24:12 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,947,844 · 21 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
2w05w06w17w210w011w112w213w315w016w218w119w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa386bf35…7e9f
0x34b655…2a6f
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xa386bf35b9…dd7e9f
Audit this contract →
← previous block·next block →recent activity