Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976d1fa364d3526be1b8ab218b940d0592edc660ad47eb4b19275f1b87fa0f10

Tx prefix hash: 234462360e81f56db91e13015ef62929fa93aef3d48982f99bbf20cba5e2dbb8
Tx public key: 9e44b6de5c1f31ee9ab9b5e7f591be2ee828ca4522b31d03181203e4e384858e
Timestamp: 1732605319 Timestamp [UCT]: 2024-11-26 07:15:19 Age [y:d:h:m:s]: 01:025:17:43:01
Block: 1161961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276847 RingCT/type: yes/0
Extra: 019e44b6de5c1f31ee9ab9b5e7f591be2ee828ca4522b31d03181203e4e384858e021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 621da309d712ddbceae636a5a1348f8250427ff5469c6174d26d273539e894e8 0.600000000000 1647616 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": 1161971, "vin": [ { "gen": { "height": 1161961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "621da309d712ddbceae636a5a1348f8250427ff5469c6174d26d273539e894e8" } } ], "extra": [ 1, 158, 68, 182, 222, 92, 31, 49, 238, 154, 185, 181, 231, 245, 145, 190, 46, 232, 40, 202, 69, 34, 179, 29, 3, 24, 18, 3, 228, 227, 132, 133, 142, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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