← previous blocknext block →recent activity
Analyzing
Block #80,776,843
14 transactions · 10 stateful · 2026-06-12 10:28:29 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,776,843 · 14 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
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x33a13d63…a8af
0x065c9d…c394
2 touches
0 conflicts
0x695b46d1…512d
0x065c9d…c394
2 touches
0 conflicts
0x96b0105d…36d1
0x065c9d…c394
2 touches
0 conflicts
0xc3303820…0860
0x065c9d…c394
2 touches
0 conflicts
0xeec7f746…80ab
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 0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block·next block →recent activity