← previous blocknext block →recent activity
Analyzing
Block #80,235,496
20 transactions · 16 stateful · 2026-06-09 22:18:53 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,235,496 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w312w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x3d4949b9…5c35
0x065c9d…c394
4 touches
2 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x81c6c16e…1173
0x065c9d…c394
4 touches
1 conflict
0x8c908fc2…0690
0x065c9d…c394
4 touches
1 conflict
0xd785ef83…adb4
0x065c9d…c394
4 touches
1 conflict
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: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity