← previous blocknext block →recent activity
Analyzing
Block #98,569,001
21 transactions · 20 stateful · 2026-08-23 20:15:15 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,569,001 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w010w112w013w114w215w316w417w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0xe4f6e7…9657
12 touches
15 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
12 touches
15 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
12 touches
15 conflicts
0x00000000…0008
0x0ea966…0742
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5784baac…ac7e
0x34b655…2a6f
6 touches
3 conflicts
0x152a2f3e…13f8
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: 0xe4f6e757…919657
15 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity