← previous blocknext block →recent activity
Analyzing
Block #98,080,013
20 transactions · 19 stateful · 2026-08-22 03:00:50 UTC
Parallelism
85/100
Blocked
32%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,080,013 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w110w012w115w218w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce519857…e5c4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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
1 conflict on slot 0xce51985741…24e5c4
Audit this contract →
← previous block·next block →recent activity