← previous blocknext block →recent activity
Analyzing
Block #98,566,159
22 transactions · 21 stateful · 2026-08-23 20:00:24 UTC
Parallelism
77/100
Blocked
19%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,566,159 · 22 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
1w010w011w112w214w317w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1641b5fc…fa40
0x34b655…2a6f
4 touches
1 conflict
0x1f00a5b3…bf76
0x34b655…2a6f
4 touches
1 conflict
0x4bb5630a…74ab
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x67209a5a…ab0e
0x34b655…2a6f
4 touches
1 conflict
0x6f413871…11a0
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity