Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99ab47c8e0d88e293aef74ef0b86a96fcb2f40a33b3279c554d8d6bd43d36382

Tx prefix hash: 5483e7e1f5c469fa45d1cc4649ee51ced06d640e6b8582842a2c28e13f302b08
Tx public key: fde99c61c23ac5ee193ecdf9ddffb23b9e433efec69a73c6d29ce645503d94a9
Timestamp: 1749043466 Timestamp [UCT]: 2025-06-04 13:24:26 Age [y:d:h:m:s]: 00:162:15:21:32
Block: 1297808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113904 RingCT/type: yes/0
Extra: 01fde99c61c23ac5ee193ecdf9ddffb23b9e433efec69a73c6d29ce645503d94a902110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7f77e774a8b0ea41e90cdfa1333ef2713ddafe6f6e3d55df4420859b750a8fc 0.600000000000 1785329 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": 1297818, "vin": [ { "gen": { "height": 1297808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7f77e774a8b0ea41e90cdfa1333ef2713ddafe6f6e3d55df4420859b750a8fc" } } ], "extra": [ 1, 253, 233, 156, 97, 194, 58, 197, 238, 25, 62, 205, 249, 221, 255, 178, 59, 158, 67, 62, 254, 198, 154, 115, 198, 210, 156, 230, 69, 80, 61, 148, 169, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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