← previous blocknext block →recent activity
Analyzing
Block #98,642,733
80 transactions · 69 stateful · 2026-08-24 02:39:08 UTC
Parallelism
79/100
Blocked
74%
Avg conflicts / tx
2.48
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,642,733 · 80 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
1w02w13w06w17w28w39w212w013w115w016w117w218w327w130w132w140w248w249w150w458w759w360w868w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x11b69a7e…334e
0xee8c0e…1242
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0x9d9f3717…44e7
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity