Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3ebcdfcd59d3cd8c5cf3f9071ae042fb7b46756abf288f05ccc8a8eb3cae2e

Tx prefix hash: 64883a1cb02c672a64daf129457687e8e5cccaf1dfb81735c11d27b98f4f6ce5
Tx public key: 82626aa00a5ac954e572f9635bfe923f3455edd8e45785a28512214cba6cee3c
Timestamp: 1626108637 Timestamp [UCT]: 2021-07-12 16:50:37 Age [y:d:h:m:s]: 03:307:05:46:26
Block: 292581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 990465 RingCT/type: yes/0
Extra: 0182626aa00a5ac954e572f9635bfe923f3455edd8e45785a28512214cba6cee3c021100000008a272b9cb000000000000000000

1 output(s) for total of 65.850365860000 dcy

stealth address amount amount idx
00: f4d1fced09ab34e71d8c4356c1d00bef7f0286fbde53adb263479fdc9e39135e 65.850365860000 613177 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": 292591, "vin": [ { "gen": { "height": 292581 } } ], "vout": [ { "amount": 65850365860, "target": { "key": "f4d1fced09ab34e71d8c4356c1d00bef7f0286fbde53adb263479fdc9e39135e" } } ], "extra": [ 1, 130, 98, 106, 160, 10, 90, 201, 84, 229, 114, 249, 99, 91, 254, 146, 63, 52, 85, 237, 216, 228, 87, 133, 162, 133, 18, 33, 76, 186, 108, 238, 60, 2, 17, 0, 0, 0, 8, 162, 114, 185, 203, 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