← previous blocknext block →recent activity
Analyzing
Block #98,426,925
21 transactions · 20 stateful · 2026-08-23 08:06:54 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,426,925 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w211w212w313w014w115w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x087c9ed9…18ee
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x56a919c4…ab49
0xe7cd86…c82d
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x695f1621…0990
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xacf82e…3500
4 touches
1 conflict
0x00000000…0001
0xacf82e…3500
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x087c9ed925…e018ee
Audit this contract →
← previous block·next block →recent activity