← previous blocknext block →recent activity
Analyzing
Block #79,116,288
14 transactions · 13 stateful · 2026-06-04 17:41:05 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,116,288 · 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
1w02w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xc8e745f5…e9f9
0x065c9d…c394
4 touches
1 conflict
0xa980598e…ec52
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xb02793…e402
4 touches
1 conflict
0x00000000…0002
0xb02793…e402
4 touches
1 conflict
0x00000000…0004
0xb02793…e402
4 touches
1 conflict
0xcd510377…571e
0xee8c0e…1242
4 touches
1 conflict
0xb823fab9…bc32
0xd32edf…ff58
3 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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity