← previous blocknext block →recent activity
Analyzing
Block #98,428,686
14 transactions · 14 stateful · 2026-08-23 08:15:46 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,428,686 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w07w08w110w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2557abf8…2901
0x34b655…2a6f
4 touches
1 conflict
0x7c82b710…e9a9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2507094f…eab4
0x34b655…2a6f
4 touches
1 conflict
0xe5fe8036…e1bd
0x34b655…2a6f
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
2 touches
0 conflicts
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 0x2557abf8e3…0a2901
Audit this contract →
← previous block·next block →recent activity