Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc6e80b69c98c1377bfec04212ebdba5ca4c7ad2f37eb8eaec6394b45208fe2

Tx prefix hash: 6c918eebb614f2159732e9b3fb13cd383fab30d0efc5185d1dfa5a736f10c610
Tx public key: 69beaf0aa122050b685f912f3d952519b2741033eee9cdb5a984822acf2a2ec3
Timestamp: 1720521582 Timestamp [UCT]: 2024-07-09 10:39:42 Age [y:d:h:m:s]: 00:311:14:45:03
Block: 1061885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222670 RingCT/type: yes/0
Extra: 0169beaf0aa122050b685f912f3d952519b2741033eee9cdb5a984822acf2a2ec302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d32aa0acf2625c95385e898653b552e2dc03d7bc87afc0840b62c780baf36d85 0.600000000000 1532384 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": 1061895, "vin": [ { "gen": { "height": 1061885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d32aa0acf2625c95385e898653b552e2dc03d7bc87afc0840b62c780baf36d85" } } ], "extra": [ 1, 105, 190, 175, 10, 161, 34, 5, 11, 104, 95, 145, 47, 61, 149, 37, 25, 178, 116, 16, 51, 238, 233, 205, 181, 169, 132, 130, 42, 207, 42, 46, 195, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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