← previous blocknext block →recent activity
Analyzing
Block #98,999,252
15 transactions · 13 stateful · 2026-08-25 08:43:10 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,999,252 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w210w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fbb72d5…155e
0x34b655…2a6f
6 touches
3 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x580c6fe7…0fe8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0eac6378…36f4
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 0x4fbb72d5c3…b1155e
Audit this contract →
← previous block·next block →recent activity