← previous blocknext block →recent activity
Analyzing
Block #98,065,271
26 transactions · 21 stateful · 2026-08-22 01:46:38 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,065,271 · 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
2w03w04w15w06w110w011w115w216w117w018w119w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xa6d40b7f…2969
0x34b655…2a6f
4 touches
1 conflict
0xaf898232…6f02
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x49299fcf…c552
0x34b655…2a6f
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
1 conflict on slot 0x9ad325f5a1…c3cc43
Audit this contract →
← previous block·next block →recent activity