← previous blocknext block →recent activity
Analyzing
Block #98,062,198
31 transactions · 28 stateful · 2026-08-22 01:31:10 UTC
Parallelism
81/100
Blocked
54%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,062,198 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w07w08w19w310w112w215w016w317w118w020w221w327w228w429w530w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xa62417ed…7db1
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xfa324e43…8898
0x1b6862…e19c
6 touches
3 conflicts
0xe5e7089a…fb91
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity