Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 06d7ecdfeca39ac74f69f01c84b0dd0b50200061dfded8acee510e731fda9064

Tx prefix hash: 73e64c03739370853bf5c2fea9069f24b0a59ef2b011c6e9c9601742f197bc24
Tx public key: 772dfdb03e171ae5f04cc6d1e64e510328c2a8de0b963c12d0824f591c55ba7d
Timestamp: 1752651898 Timestamp [UTC]: 2025-07-16 07:44:58 Age [y:d:h:m:s]: 01:123:23:07:07
Block: 1326577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353635 RingCT/type: yes/0
Extra: 01772dfdb03e171ae5f04cc6d1e64e510328c2a8de0b963c12d0824f591c55ba7d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65b8d5bbecdb08a8f0ad52f3acce4474852f96df6d28e09237eb649f13b2f1d0 0.000600000000 1814328 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1326587, "vin": [ { "gen": { "height": 1326577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b8d5bbecdb08a8f0ad52f3acce4474852f96df6d28e09237eb649f13b2f1d0" } } ], "extra": [ 1, 119, 45, 253, 176, 62, 23, 26, 229, 240, 76, 198, 209, 230, 78, 81, 3, 40, 194, 168, 222, 11, 150, 60, 18, 208, 130, 79, 89, 28, 85, 186, 125, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: