← previous blocknext block →recent activity
Analyzing
Block #99,209,242
14 transactions · 10 stateful · 2026-08-26 02:26:04 UTC
Parallelism
86/100
Blocked
10%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,209,242 · 14 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
2w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa45564d6…2082
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0xd01d67e2…d661
0x065c9d…c394
2 touches
0 conflicts
0xdbd9d3f7…b9e7
0x065c9d…c394
2 touches
0 conflicts
0xf412af30…a5f2
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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 0xa45564d645…9a2082
Audit this contract →
← previous block·next block →recent activity