← previous blocknext block →recent activity
Analyzing
Block #80,241,050
15 transactions · 12 stateful · 2026-06-09 22:55:51 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,241,050 · 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
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x243e7fcb…2b0f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
3 touches
1 conflict
0x7b3491f1…7f6b
0x065c9d…c394
3 touches
1 conflict
0x200d5b70…89d8
0x065c9d…c394
2 touches
0 conflicts
0x566374ad…53be
0x065c9d…c394
2 touches
0 conflicts
0xc05b9adf…d95f
0x065c9d…c394
2 touches
0 conflicts
0xd444d2e4…be40
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 0x243e7fcbe0…3c2b0f
Audit this contract →
← previous block·next block →recent activity