← previous blocknext block →recent activity
Analyzing
Block #79,250,124
20 transactions · 17 stateful · 2026-06-05 08:33:34 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,250,124 · 20 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
1w02w13w14w05w16w27w29w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeea0f300…ec6e
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb0e9898d…42c2
0xa6afd3…d132
4 touches
1 conflict
0xde6b917f…3a72
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
1 conflict on slot 0xeea0f300d0…4aec6e
Audit this contract →
← previous block·next block →recent activity