← previous blocknext block →recent activity
Analyzing
Block #98,525,493
72 transactions · 62 stateful · 2026-08-23 16:28:21 UTC
Parallelism
79/100
Blocked
73%
Avg conflicts / tx
2.4
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,525,493 · 72 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w29w012w013w114w215w316w417w118w219w345w446w547w850w952w1053w154w1157w1258w1359w1465w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0xbb3f3c…e046
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0x705a9a1a…db08
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3c2892bf…9a20
0x34b655…2a6f
10 touches
10 conflicts
0x6063a926…0be4
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity