← previous blocknext block →recent activity
Analyzing
Block #98,431,946
26 transactions · 23 stateful · 2026-08-23 08:32:10 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,431,946 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w110w011w112w316w017w120w221w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb27e400d…f51d
0x34b655…2a6f
6 touches
3 conflicts
0x5771b06f…14ce
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd8ef5843…3369
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
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
3 conflicts on slot 0xb27e400d54…27f51d
Audit this contract →
← previous block·next block →recent activity