← previous blocknext block →recent activity
Analyzing
Block #98,391,386
19 transactions · 17 stateful · 2026-08-23 05:08:06 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,391,386 · 19 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
3w04w111w212w013w316w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e069edf…ddac
0x34b655…2a6f
6 touches
3 conflicts
0x676b5eb4…0b33
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0x4e069edf7d…52ddac
Audit this contract →
← previous block·next block →recent activity