← previous blocknext block →recent activity
Analyzing
Block #80,760,962
24 transactions · 18 stateful · 2026-06-12 08:42:39 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,760,962 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w07w38w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x9dc0b4e1…3a7a
0x065c9d…c394
4 touches
1 conflict
0x6cd61259…e3f2
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity