← previous blocknext block →recent activity
Analyzing
Block #98,490,691
23 transactions · 21 stateful · 2026-08-23 13:28:04 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,490,691 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w17w08w19w011w115w216w218w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x627738d1…db02
0x34b655…2a6f
6 touches
3 conflicts
0xfd5482c3…7e73
0x34b655…2a6f
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x02a46223…6845
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x0e3b59e9…d9d0
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity