Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 682b97254baaa71f53daaa962f36e58d6ad3b9712d7d079c668cd07d7432a0e0

Tx prefix hash: 800c71fa94e55fc7fec2561680e889a6929d0d9184f2b6f37de3ba6b42641822
Tx public key: c138a7a0eabbd13001f05452e7f04b8c8ac050358fada6f3d8ddeba7627d8101
Timestamp: 1574091351 Timestamp [UCT]: 2019-11-18 15:35:51 Age [y:d:h:m:s]: 05:058:20:30:47
Block: 11617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1185538 RingCT/type: yes/0
Extra: 01c138a7a0eabbd13001f05452e7f04b8c8ac050358fada6f3d8ddeba7627d8101021100000002ccefb800000000000000000000

1 output(s) for total of 561.705848342000 dcy

stealth address amount amount idx
00: 46f6da1e3c7f6e86a086c73d68e460bf07df551f6e0ca54279f00fb92ef83892 561.705848342000 12694 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": 11627, "vin": [ { "gen": { "height": 11617 } } ], "vout": [ { "amount": 561705848342, "target": { "key": "46f6da1e3c7f6e86a086c73d68e460bf07df551f6e0ca54279f00fb92ef83892" } } ], "extra": [ 1, 193, 56, 167, 160, 234, 187, 209, 48, 1, 240, 84, 82, 231, 240, 75, 140, 138, 192, 80, 53, 143, 173, 166, 243, 216, 221, 235, 167, 98, 125, 129, 1, 2, 17, 0, 0, 0, 2, 204, 239, 184, 0, 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