← previous blocknext block →recent activity
Analyzing
Block #99,081,077
15 transactions · 13 stateful · 2026-08-25 15:41:01 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,081,077 · 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
1w08w09w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x733edb92…4e80
0x34b655…2a6f
4 touches
1 conflict
0xb66d168c…56de
0x065c9d…c394
3 touches
1 conflict
0x3610ec01…67b9
0x065c9d…c394
2 touches
0 conflicts
0x3908ebff…f19a
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x5e12e715…fba5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity