← previous blocknext block →recent activity
Analyzing
Block #80,745,055
8 transactions · 7 stateful · 2026-06-12 06:56:37 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,745,055 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe3fde5f6…a7e8
0x065c9d…c394
3 touches
1 conflict
0x6fe24256…bd11
0x065c9d…c394
3 touches
1 conflict
0x3a0d585b…3400
0x065c9d…c394
2 touches
0 conflicts
0x58762d07…81c6
0x065c9d…c394
2 touches
0 conflicts
0x76654fe3…e518
0x065c9d…c394
2 touches
0 conflicts
0xf3adf170…0f49
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity