← previous blocknext block →recent activity
Analyzing
Block #99,361,483
16 transactions · 11 stateful · 2026-08-26 15:12:12 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,361,483 · 16 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x018ba6ae…8575
0x065c9d…c394
4 touches
1 conflict
0xa61973c4…70e1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf1b4d3fb…313f
0x065c9d…c394
3 touches
1 conflict
0x0ba7e362…0f8a
0x065c9d…c394
3 touches
1 conflict
0x0c367272…aa37
0x065c9d…c394
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x018ba6aee8…1d8575
Audit this contract →
← previous block·next block →recent activity