Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d9d1899f5259deb1473f40e1f4a68139cae47aeb61f3d195a53ce8efd51a3bb

Tx prefix hash: c2a1dc6fb4412e6adb329bade0e593202b872b17d2c5c9fc75d5537a695b8ee6
Tx public key: f3f8f920e99b9e054489da93a203e98615d2ff09dd96e0a0cbc9a9b23f9b8c8a
Timestamp: 1705064545 Timestamp [UCT]: 2024-01-12 13:02:25 Age [y:d:h:m:s]: 01:362:04:59:01
Block: 933721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517779 RingCT/type: yes/0
Extra: 01f3f8f920e99b9e054489da93a203e98615d2ff09dd96e0a0cbc9a9b23f9b8c8a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52504258e88a5ff7b0b4400e028769501194155a555e42b38eb17cf57eac4224 0.600000000000 1391691 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": 933731, "vin": [ { "gen": { "height": 933721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52504258e88a5ff7b0b4400e028769501194155a555e42b38eb17cf57eac4224" } } ], "extra": [ 1, 243, 248, 249, 32, 233, 155, 158, 5, 68, 137, 218, 147, 162, 3, 233, 134, 21, 210, 255, 9, 221, 150, 224, 160, 203, 201, 169, 178, 63, 155, 140, 138, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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