Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5160b5cb02ea4d2fbb87af5ac6c8eafb498365bd3dceb09a3c4574489e9ed1

Tx prefix hash: 713cc2dbf7e9211e4c6bda7bff1d5aa898493c6d21e92ae39a465956e054b4f8
Tx public key: ae5147b3545ccbd1710a9dce757241d48c05fb9734ef31e8d2c444875c2497d9
Timestamp: 1699834015 Timestamp [UCT]: 2023-11-13 00:06:55 Age [y:d:h:m:s]: 01:152:03:40:37
Block: 890377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369921 RingCT/type: yes/0
Extra: 01ae5147b3545ccbd1710a9dce757241d48c05fb9734ef31e8d2c444875c2497d902110000000102d75dd9000000000000000000

1 output(s) for total of 0.688353276000 dcy

stealth address amount amount idx
00: 73e97c6ffcca57bf90a1a4dd1ced7c3f31bf36bf7c353a3da5ba37d1d7ec5825 0.688353276000 1346400 of 0

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": 890387, "vin": [ { "gen": { "height": 890377 } } ], "vout": [ { "amount": 688353276, "target": { "key": "73e97c6ffcca57bf90a1a4dd1ced7c3f31bf36bf7c353a3da5ba37d1d7ec5825" } } ], "extra": [ 1, 174, 81, 71, 179, 84, 92, 203, 209, 113, 10, 157, 206, 117, 114, 65, 212, 140, 5, 251, 151, 52, 239, 49, 232, 210, 196, 68, 135, 92, 36, 151, 217, 2, 17, 0, 0, 0, 1, 2, 215, 93, 217, 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