← previous blocknext block →recent activity
Analyzing
Block #98,069,450
25 transactions · 22 stateful · 2026-08-22 02:07:40 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,069,450 · 25 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
1w02w03w14w05w06w115w016w117w118w220w321w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x732ef63b…29c6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9aa7036b…a2a7
0xa6afd3…d132
6 touches
3 conflicts
0xadce6355…03bf
0xa6afd3…d132
6 touches
3 conflicts
0x29cd05f5…390c
0x34b655…2a6f
6 touches
3 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xea7ebe9d…709e
0x2b46c0…1669
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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 0x732ef63b2a…f729c6
Audit this contract →
← previous block·next block →recent activity