← previous blocknext block →recent activity
Analyzing
Block #98,334,075
39 transactions · 36 stateful · 2026-08-23 00:19:47 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,334,075 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w413w014w115w516w617w018w121w622w023w124w233w634w738w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf31ab9b0…a087
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
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