← previous blocknext block →recent activity
Analyzing
Block #98,015,755
61 transactions · 50 stateful · 2026-08-21 21:37:20 UTC
Parallelism
72/100
Blocked
74%
Avg conflicts / tx
3.31
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,015,755 · 61 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
1w02w05w07w19w210w311w412w513w614w717w818w919w1020w1121w1222w1323w1424w1526w1633w237w340w441w560w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
34 touches
136 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c2
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 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
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity