← previous blocknext block →recent activity
Analyzing
Block #80,953,586
12 transactions · 9 stateful · 2026-06-13 06:07:09 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,953,586 · 12 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
1w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6cbd68b6…ed81
0x065c9d…c394
4 touches
1 conflict
0x2c14c7cf…dd0e
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0xffce8d35…ef34
0x0594c7…a3be
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
2 touches
0 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
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 0xef65bff33c…857c9d
Audit this contract →
← previous block·next block →recent activity