← previous blocknext block →recent activity
Analyzing
Block #98,748,435
67 transactions · 52 stateful · 2026-08-24 11:40:40 UTC
Parallelism
75/100
Blocked
73%
Avg conflicts / tx
2.75
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,748,435 · 67 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w320w421w522w623w724w825w926w1027w1130w1231w1336w849w1450w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xfcfec71a…b24c
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0019
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0029
0x1b6862…e19c
16 touches
28 conflicts
0x4e7eb462…b2ab
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
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: Kuru Exchange: MarginAccount
66 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity