← previous blocknext block →recent activity
Analyzing
Block #98,097,569
18 transactions · 17 stateful · 2026-08-22 04:29:10 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,097,569 · 18 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
1w03w14w05w06w18w013w214w115w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd603f6f…256d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0xfe37be0f…4fa0
0x065c9d…c394
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
3 conflicts on slot 0xdd603f6fc5…28256d
Audit this contract →
← previous block·next block →recent activity