← previous blocknext block →recent activity
Analyzing
Block #98,288,399
22 transactions · 19 stateful · 2026-08-22 20:29:56 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,288,399 · 22 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
2w04w05w16w07w111w012w114w219w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf37f77e…a027
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3f81bcfb…2905
0x40c49f…2af0
4 touches
1 conflict
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0x06ce5d4b…c122
0x2b46c0…1669
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x05b1b07a…7a99
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 0xcf37f77e49…18a027
Audit this contract →
← previous block·next block →recent activity