← previous blocknext block →recent activity
Analyzing
Block #98,606,468
22 transactions · 19 stateful · 2026-08-23 23:30:31 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,606,468 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w19w210w311w212w013w114w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f4b1c7a…fa1c
0x34b655…2a6f
10 touches
10 conflicts
0x24bb46f7…3853
0x34b655…2a6f
8 touches
6 conflicts
0x81f91b12…8f2a
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x5f4b1c7ab7…7cfa1c
Audit this contract →
← previous block·next block →recent activity