Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d14d4a3fa372540e94b829f6c9d2645566c5d5dd5ef423331b3a3ad97469953

Tx prefix hash: 918edd31064c3f966c029dee11085958d602c1d52e60cc50641e4a33ea0ee5e8
Tx public key: ab7b1c04178f4ee52ff13e4161ebf55b230c329c8c805d7406c7bc84fcdb829e
Timestamp: 1708556323 Timestamp [UCT]: 2024-02-21 22:58:43 Age [y:d:h:m:s]: 01:046:07:03:54
Block: 962680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294101 RingCT/type: yes/0
Extra: 01ab7b1c04178f4ee52ff13e4161ebf55b230c329c8c805d7406c7bc84fcdb829e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f31f775cc70e388214cc9f0570b04d70d57bb1407ad2c3ea703c0528fb028c85 0.600000000000 1422355 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": 962690, "vin": [ { "gen": { "height": 962680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f31f775cc70e388214cc9f0570b04d70d57bb1407ad2c3ea703c0528fb028c85" } } ], "extra": [ 1, 171, 123, 28, 4, 23, 143, 78, 229, 47, 241, 62, 65, 97, 235, 245, 91, 35, 12, 50, 156, 140, 128, 93, 116, 6, 199, 188, 132, 252, 219, 130, 158, 2, 17, 0, 0, 0, 1, 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