← previous blocknext block →recent activity
Analyzing
Block #79,418,483
30 transactions · 19 stateful · 2026-06-06 03:19:43 UTC
Parallelism
87/100
Blocked
16%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,418,483 · 30 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
3w04w16w07w09w214w017w3
- 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
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xb766644d…eaa9
0xd32edf…ff58
3 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0x9b55ff70…01a2
0x065c9d…c394
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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