← previous blocknext block →recent activity
Analyzing
Block #98,495,520
41 transactions · 34 stateful · 2026-08-23 13:52:22 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.39
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,495,520 · 41 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
1w02w14w05w17w09w110w211w012w113w116w017w019w222w123w124w328w129w230w331w432w533w634w735w837w1039w1240w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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: Perpl
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity