← previous blocknext block →recent activity
Analyzing
Block #98,081,334
41 transactions · 25 stateful · 2026-08-22 03:07:29 UTC
Parallelism
90/100
Blocked
40%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,081,334 · 41 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
1w03w06w07w09w011w012w118w019w120w225w026w127w129w230w233w337w140w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eaed5a0…9f17
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xdb3aded4…2c79
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0x9eaed5a054…529f17
Audit this contract →
← previous block·next block →recent activity