← previous blocknext block →recent activity
Analyzing
Block #98,021,014
32 transactions · 18 stateful · 2026-08-21 22:03:49 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,021,014 · 32 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
6w08w09w013w014w119w120w221w124w329w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4705062a…84be
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xf0df636e…1c30
0x34b655…2a6f
4 touches
1 conflict
0xfeac3ee8…6570
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3f81bcfb…2905
0x40c49f…2af0
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 0x4705062a20…e284be
Audit this contract →
← previous block·next block →recent activity