← previous blocknext block →recent activity
Analyzing
Block #98,013,799
67 transactions · 50 stateful · 2026-08-21 21:27:29 UTC
Parallelism
79/100
Blocked
68%
Avg conflicts / tx
1.54
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,013,799 · 67 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w07w09w112w213w315w417w519w621w722w823w928w129w231w333w250w454w466w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity