Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0af26c0776b72cc923dc892b7c5506d69317e9173a51b6af801a86c68f7dac0

Tx prefix hash: 5fc644c22252bb4d2f5a248a2f314d033e505fe126174ef660bec039e7a51127
Tx public key: a68f9d17309d38aa4c023cdfde993156cd59460bdcffbb5e887d46378a0f3ac8
Timestamp: 1638485903 Timestamp [UCT]: 2021-12-02 22:58:23 Age [y:d:h:m:s]: 03:337:03:22:13
Block: 387101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1017377 RingCT/type: yes/0
Extra: 01a68f9d17309d38aa4c023cdfde993156cd59460bdcffbb5e887d46378a0f3ac802110000000a379224c2000000000000000000

1 output(s) for total of 32.016515508000 dcy

stealth address amount amount idx
00: 8976050a39f5b28ce7f159ebb4be002ba96c5a575cf0b495ed2fc4c7a87c2b4d 32.016515508000 780828 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": 387111, "vin": [ { "gen": { "height": 387101 } } ], "vout": [ { "amount": 32016515508, "target": { "key": "8976050a39f5b28ce7f159ebb4be002ba96c5a575cf0b495ed2fc4c7a87c2b4d" } } ], "extra": [ 1, 166, 143, 157, 23, 48, 157, 56, 170, 76, 2, 60, 223, 222, 153, 49, 86, 205, 89, 70, 11, 220, 255, 187, 94, 136, 125, 70, 55, 138, 15, 58, 200, 2, 17, 0, 0, 0, 10, 55, 146, 36, 194, 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