← previous blocknext block →recent activity
Analyzing
Block #98,774,656
55 transactions · 37 stateful · 2026-08-24 13:52:43 UTC
Parallelism
71/100
Blocked
76%
Avg conflicts / tx
2.13
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,774,656 · 55 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w413w525w127w530w634w639w642w751w1252w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0x4423a307…9f44
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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: 0xbb3f3cb7…74e046
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity