← previous blocknext block →recent activity
Analyzing
Block #80,246,910
15 transactions · 11 stateful · 2026-06-09 23:34:55 UTC
Parallelism
87/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,246,910 · 15 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x5922c4c7…5ce4
0xd32edf…ff58
3 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0xeda2edc3…91d8
0x000000…012a
2 touches
0 conflicts
0x81308cb5…f43b
0x065c9d…c394
2 touches
0 conflicts
0x9bd62ea7…b185
0x065c9d…c394
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
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