Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aadd8d04fe6cb06ea5ecd7d891f0ec89d253fd3c3aee1a4ba3f1c4b467fbb83b

Tx prefix hash: 50a04589f0b01db3b51d7177c56251316481ba7ea10a2a70e8b82a97f4279ba9
Tx public key: 35614187e9523fc5f48a906d2839f11a018ebf0d622dd506f79b17c81071ce2a
Timestamp: 1718096140 Timestamp [UTC]: 2024-06-11 08:55:40 Age [y:d:h:m:s]: 02:156:20:44:12
Block: 1041780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636893 RingCT/type: yes/0
Extra: 0135614187e9523fc5f48a906d2839f11a018ebf0d622dd506f79b17c81071ce2a02110000000352d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 229260205863b2f96dc224aa442fab4ccdcb5775d1bf70506b53c2d70f1d79db 0.000600000000 1510537 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": 1041790, "vin": [ { "gen": { "height": 1041780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229260205863b2f96dc224aa442fab4ccdcb5775d1bf70506b53c2d70f1d79db" } } ], "extra": [ 1, 53, 97, 65, 135, 233, 82, 63, 197, 244, 138, 144, 109, 40, 57, 241, 26, 1, 142, 191, 13, 98, 45, 213, 6, 247, 155, 23, 200, 16, 113, 206, 42, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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: