← previous blocknext block →recent activity
Analyzing
Block #79,419,471
17 transactions · 14 stateful · 2026-06-06 03:26:17 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,419,471 · 17 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
2w05w16w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a8b487…3f4d
0x065c9d…c394
2 touches
0 conflicts
0x5ae4d2b6…9bc5
0x065c9d…c394
2 touches
0 conflicts
0x85fa62ab…8a07
0x065c9d…c394
2 touches
0 conflicts
0xa4c61866…e044
0x065c9d…c394
2 touches
0 conflicts
0xbad70b7f…57a5
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity