Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61efc6a858a9159ff99fb89bcadd2bd18e1ea66c250fc7243fb9ac757264c503

Tx prefix hash: c66ce43c291ff959744de951d16df914c78faeabc23fd98a890e14fbb38ffc89
Tx public key: 6dd08720ac1a14be9e68b65d056ead08c6082ade1753edc55b0b405456b4a0df
Timestamp: 1765334654 Timestamp [UCT]: 2025-12-10 02:44:14 Age [y:d:h:m:s]: 00:025:13:17:30
Block: 1430263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18320 RingCT/type: yes/0
Extra: 016dd08720ac1a14be9e68b65d056ead08c6082ade1753edc55b0b405456b4a0df021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdfbf7c7068229502b671885b5938b5fff4f2006f32903f6573158b8e8bdbffe 0.600000000000 1919012 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 dinasty-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": 1430273, "vin": [ { "gen": { "height": 1430263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdfbf7c7068229502b671885b5938b5fff4f2006f32903f6573158b8e8bdbffe" } } ], "extra": [ 1, 109, 208, 135, 32, 172, 26, 20, 190, 158, 104, 182, 93, 5, 110, 173, 8, 198, 8, 42, 222, 23, 83, 237, 197, 91, 11, 64, 84, 86, 180, 160, 223, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8