Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5dc52690899cd8ad2e04f39c4962575303858ea6bbcf41a57e271965bdc6400

Tx prefix hash: 06c7d3a959f70dce904022a8c45c947dbb7dabfa2bc5b9709957808fd6123932
Tx public key: 01394f62e498fed3cc937028ef56b585fa8f4c0725991f5373e0d6aff795d1bd
Timestamp: 1578637674 Timestamp [UCT]: 2020-01-10 06:27:54 Age [y:d:h:m:s]: 05:062:23:41:54
Block: 42271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195216 RingCT/type: yes/0
Extra: 0101394f62e498fed3cc937028ef56b585fa8f4c0725991f5373e0d6aff795d1bd021100000004d81c26c0000000000000000000

1 output(s) for total of 444.569304962000 dcy

stealth address amount amount idx
00: afcc725afe12a1e7f9bf134396c259527e6d8c4a8c01dfcc3120e4e958428c10 444.569304962000 76079 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": 42281, "vin": [ { "gen": { "height": 42271 } } ], "vout": [ { "amount": 444569304962, "target": { "key": "afcc725afe12a1e7f9bf134396c259527e6d8c4a8c01dfcc3120e4e958428c10" } } ], "extra": [ 1, 1, 57, 79, 98, 228, 152, 254, 211, 204, 147, 112, 40, 239, 86, 181, 133, 250, 143, 76, 7, 37, 153, 31, 83, 115, 224, 214, 175, 247, 149, 209, 189, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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