← previous blocknext block →recent activity
Analyzing
Block #98,060,599
69 transactions · 47 stateful · 2026-08-22 01:23:07 UTC
Parallelism
80/100
Blocked
68%
Avg conflicts / tx
1.35
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,060,599 · 69 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
1w03w011w013w014w116w019w220w124w026w227w128w029w130w231w132w238w239w145w449w551w352w653w262w968w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
18 touches
36 conflicts
0xf3d10975…0d07
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
12 touches
15 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
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: Perpl
36 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity