← previous blocknext block →recent activity
Analyzing
Block #98,929,927
14 transactions · 13 stateful · 2026-08-25 02:54:05 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,929,927 · 14 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
1w02w13w04w07w18w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3a429191…9cda
0x34b655…2a6f
6 touches
3 conflicts
0x8488f10f…9353
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
4 touches
1 conflict
0xc20bd100…8b0e
0x2b46c0…1669
4 touches
1 conflict
0x1ba691f2…08bb
0x34b655…2a6f
4 touches
1 conflict
0x52061a32…cc8b
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity