← previous blocknext block →recent activity
Analyzing
Block #80,101,714
9 transactions · 7 stateful · 2026-06-09 07:27:04 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,101,714 · 9 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
1w03w14w2
- 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
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xc8eba81e…8f67
0x065c9d…c394
4 touches
1 conflict
0x4bf190a4…15a2
0x065c9d…c394
3 touches
1 conflict
0x7125c9c4…3fed
0x065c9d…c394
3 touches
1 conflict
0x976b8eb8…130a
0x065c9d…c394
2 touches
0 conflicts
0x9bbd7582…2f06
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity