← previous blocknext block →recent activity
Analyzing
Block #98,840,773
22 transactions · 22 stateful · 2026-08-24 19:25:34 UTC
Parallelism
73/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,840,773 · 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
3w04w15w16w28w29w313w414w520w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d5fcf59…7fb9
0x34b655…2a6f
8 touches
6 conflicts
0xe5db3dd9…ecf2
0x34b655…2a6f
8 touches
6 conflicts
0x04994ed2…9032
0x34b655…2a6f
6 touches
3 conflicts
0xb75d08b2…3e12
0x34b655…2a6f
6 touches
3 conflicts
0xd984a5e4…5cfc
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x1d5fcf5942…e07fb9
Audit this contract →
← previous block·next block →recent activity