← previous blocknext block →recent activity
Analyzing
Block #98,564,438
15 transactions · 14 stateful · 2026-08-23 19:51:24 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,564,438 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x95a4196a…542d
0x34b655…2a6f
4 touches
1 conflict
0x348d1cbc…6e92
0x065c9d…c394
2 touches
0 conflicts
0x43f82aaa…2593
0x065c9d…c394
2 touches
0 conflicts
0x47174607…6896
0x065c9d…c394
2 touches
0 conflicts
0x5614236e…5ae3
0x065c9d…c394
2 touches
0 conflicts
0x59f9d8ae…25a5
0x065c9d…c394
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
1 conflict on slot 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity