← previous blocknext block →recent activity
Analyzing
Block #80,230,364
10 transactions · 7 stateful · 2026-06-09 21:44:26 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,230,364 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0x485d6a0e…963a
0x065c9d…c394
2 touches
0 conflicts
0x91eba5ff…3997
0x065c9d…c394
2 touches
0 conflicts
0xf62ac630…fd7f
0x065c9d…c394
2 touches
0 conflicts
0x1ea0a6bc…6a74
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: MarginAccount
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity