Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf71ad9267aaec175182ac147e42ef1b51c41c6dc42af526f5227e85002a7aec

Tx prefix hash: da6462daa9c8d9ea66084eb422976c9800842cf6434b404c26e282d054a31c1e
Tx public key: d0ab51bc53d46fd1a5ca486eee932cbdf0f78c85fcccfd69c901e8527028052e
Timestamp: 1577179372 Timestamp [UCT]: 2019-12-24 09:22:52 Age [y:d:h:m:s]: 05:013:18:56:56
Block: 30546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159956 RingCT/type: yes/0
Extra: 01d0ab51bc53d46fd1a5ca486eee932cbdf0f78c85fcccfd69c901e8527028052e0211000000028a2ee0d9000000000000000000

1 output(s) for total of 486.179651429000 dcy

stealth address amount amount idx
00: 3416920030ae4741859a49165ee5dfba7a54b8ff88213800f8676a186c20b12a 486.179651429000 50440 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": 30556, "vin": [ { "gen": { "height": 30546 } } ], "vout": [ { "amount": 486179651429, "target": { "key": "3416920030ae4741859a49165ee5dfba7a54b8ff88213800f8676a186c20b12a" } } ], "extra": [ 1, 208, 171, 81, 188, 83, 212, 111, 209, 165, 202, 72, 110, 238, 147, 44, 189, 240, 247, 140, 133, 252, 204, 253, 105, 201, 1, 232, 82, 112, 40, 5, 46, 2, 17, 0, 0, 0, 2, 138, 46, 224, 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