Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 309b4df20528f7dc1bce3bba68d76edeafbd9fd21fc57e748aa82afd7eaa9b10

Tx prefix hash: b7c68d9d3e0cc1184b177e4833383069242965a43fa8a671671b0a56d95a9b83
Tx public key: d725458e5cdfbd5eb334824a570245b1cc4d3b91f35cc805fd20b3139a3c04dd
Timestamp: 1708996694 Timestamp [UCT]: 2024-02-27 01:18:14 Age [y:d:h:m:s]: 01:111:10:00:20
Block: 966343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340577 RingCT/type: yes/0
Extra: 01d725458e5cdfbd5eb334824a570245b1cc4d3b91f35cc805fd20b3139a3c04dd02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 231e0e4c23a54780f316686fa60af987608324d7a48687b56bb19ef74c00b974 0.600000000000 1426100 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": 966353, "vin": [ { "gen": { "height": 966343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "231e0e4c23a54780f316686fa60af987608324d7a48687b56bb19ef74c00b974" } } ], "extra": [ 1, 215, 37, 69, 142, 92, 223, 189, 94, 179, 52, 130, 74, 87, 2, 69, 177, 204, 77, 59, 145, 243, 92, 200, 5, 253, 32, 179, 19, 154, 60, 4, 221, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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