← previous blocknext block →recent activity
Analyzing
Block #79,408,352
16 transactions · 14 stateful · 2026-06-06 02:12:10 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,408,352 · 16 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
1w02w13w25w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x73ab2e58…ccd7
0x065c9d…c394
6 touches
3 conflicts
0x5b4b3fa7…2f73
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x85717a…a0f7
4 touches
1 conflict
0x00000000…0004
0x85717a…a0f7
4 touches
1 conflict
0x00000000…0000
0x85717a…a0f7
4 touches
1 conflict
0xf8127de7…d5ec
0x3bd359…433a
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity