← previous blocknext block →recent activity
Analyzing
Block #98,091,924
38 transactions · 35 stateful · 2026-08-22 04:00:46 UTC
Parallelism
66/100
Blocked
60%
Avg conflicts / tx
2.37
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,091,924 · 38 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w27w08w310w011w112w213w015w017w122w023w125w126w227w328w431w732w833w934w1035w1136w1237w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0x17c93766…889e
0x34b655…2a6f
8 touches
6 conflicts
0x1da7723c…80ab
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x6fc24f20…f3c7
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity