Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a447284aa9eed83ac4120864e1fe9d4045ac55fa8bd27f68647a8a3cf641ab68

Tx prefix hash: 6c337b47db303701bec6dd42ead08c6af57d7e1110990e14cda5007adf0dfbda
Tx public key: 7ab05db0f73f5eb0c849ad3495d5c28af0104e37f61b14e756b1d433a20f4ee1
Timestamp: 1721249524 Timestamp [UTC]: 2024-07-17 20:52:04 Age [y:d:h:m:s]: 02:127:11:51:14
Block: 1067922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 615572 RingCT/type: yes/0
Extra: 017ab05db0f73f5eb0c849ad3495d5c28af0104e37f61b14e756b1d433a20f4ee102110000000c91e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a5ad9b1063f859dc0e9cb1cfcd68bc090ff1870b33645dfca9292148c74d980 0.000600000000 1538871 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": 1067932, "vin": [ { "gen": { "height": 1067922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a5ad9b1063f859dc0e9cb1cfcd68bc090ff1870b33645dfca9292148c74d980" } } ], "extra": [ 1, 122, 176, 93, 176, 247, 63, 94, 176, 200, 73, 173, 52, 149, 213, 194, 138, 240, 16, 78, 55, 246, 27, 20, 231, 86, 177, 212, 51, 162, 15, 78, 225, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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: