← previous blocknext block →recent activity
Analyzing
Block #80,755,039
19 transactions · 12 stateful · 2026-06-12 08:03:08 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,755,039 · 19 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
1w02w06w17w2
- 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
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xfee023fb…2712
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
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