← previous blocknext block →recent activity
Analyzing
Block #98,570,733
10 transactions · 10 stateful · 2026-08-23 20:24:20 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,570,733 · 10 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
1w02w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6dedaff6…161b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x002a2f7f…bc85
0x34b655…2a6f
2 touches
0 conflicts
0x19432f1e…b28d
0x34b655…2a6f
2 touches
0 conflicts
0x3ca268be…8865
0x34b655…2a6f
2 touches
0 conflicts
0x437812ac…80d9
0x34b655…2a6f
2 touches
0 conflicts
0x50c61506…343f
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity