Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d62e8c34c25e47874079a5c3701aaa901fd5be02b5b08d4f4cf8f0cc9306af4

Tx prefix hash: d9d4c5879f1be8a4a38e3855115b43debb049e4bc3ea41c70ba4dbd1e17ba90a
Tx public key: cce58514f5e2592bd88db5ff083fe1a281c34a9b3205f18fb595b9e6d5ea8c4a
Timestamp: 1577693827 Timestamp [UCT]: 2019-12-30 08:17:07 Age [y:d:h:m:s]: 05:000:11:00:50
Block: 34866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150343 RingCT/type: yes/0
Extra: 01cce58514f5e2592bd88db5ff083fe1a281c34a9b3205f18fb595b9e6d5ea8c4a0211000000038a2ee0d9000000000000000000

1 output(s) for total of 470.408676565000 dcy

stealth address amount amount idx
00: e4259124b856562a17d1e03419f1457c244db05d594d2222abb675cecee57fd6 470.408676565000 58751 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": 34876, "vin": [ { "gen": { "height": 34866 } } ], "vout": [ { "amount": 470408676565, "target": { "key": "e4259124b856562a17d1e03419f1457c244db05d594d2222abb675cecee57fd6" } } ], "extra": [ 1, 204, 229, 133, 20, 245, 226, 89, 43, 216, 141, 181, 255, 8, 63, 225, 162, 129, 195, 74, 155, 50, 5, 241, 143, 181, 149, 185, 230, 213, 234, 140, 74, 2, 17, 0, 0, 0, 3, 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