← previous blocknext block →recent activity
Analyzing
Block #98,081,645
25 transactions · 21 stateful · 2026-08-22 03:09:02 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,081,645 · 25 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
2w04w05w06w17w210w011w113w114w115w220w221w022w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53eac009…b61b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x4458bf9f…f775
0xd32edf…ff58
5 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x53eac00933…f3b61b
Audit this contract →
← previous block·next block →recent activity