← previous blocknext block →recent activity
Analyzing
Block #98,202,273
14 transactions · 13 stateful · 2026-08-22 13:16:40 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,202,273 · 14 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
1w04w05w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd5c557…de1e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1aa85bda…e324
0x34b655…2a6f
2 touches
0 conflicts
0x1e6db1fe…8d8b
0x34b655…2a6f
2 touches
0 conflicts
0x1eced4db…6e94
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x97da0e96…a419
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 0x0bd5c55710…26de1e
Audit this contract →
← previous block·next block →recent activity