← previous blocknext block →recent activity
Analyzing
Block #98,532,201
22 transactions · 20 stateful · 2026-08-23 17:03:11 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,532,201 · 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
1w02w13w27w010w113w214w315w416w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc61e213f…6e7b
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0x51a9c528…d9c3
0x34b655…2a6f
6 touches
3 conflicts
0x0016aad3…dd56
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c4
0x1b6862…e19c
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity