Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72cc801530a744d493b8b3aaf7675e0879661f5becf96faf132d8812655d7a3

Tx prefix hash: 740d0fab926bf19f4dc6892e6dda76a707999d47eab56ce6eb93c5fa52f15daa
Tx public key: 7a868c4e6fea583fd486f4036ddd8585d0ae374882a40a037554279c57a1eb17
Timestamp: 1707610267 Timestamp [UCT]: 2024-02-11 00:11:07 Age [y:d:h:m:s]: 01:282:23:38:43
Block: 954831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461031 RingCT/type: yes/0
Extra: 017a868c4e6fea583fd486f4036ddd8585d0ae374882a40a037554279c57a1eb170211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64fdc8aebc1199ef9c5d5e85b885318d13b6d6384e2a829ba96b89b44456179b 0.600000000000 1414113 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": 954841, "vin": [ { "gen": { "height": 954831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64fdc8aebc1199ef9c5d5e85b885318d13b6d6384e2a829ba96b89b44456179b" } } ], "extra": [ 1, 122, 134, 140, 78, 111, 234, 88, 63, 212, 134, 244, 3, 109, 221, 133, 133, 208, 174, 55, 72, 130, 164, 10, 3, 117, 84, 39, 156, 87, 161, 235, 23, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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