Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2021e961a61300c1e0839ef5ccc3b715fe2f7c946a31fe056efb2aec8220a1b1

Tx prefix hash: a82ead77255f2115e349621c5383763ca675b9cc292c8411a20ad9602bd8d8d0
Tx public key: 9655e6561cc077a87295cfaabcd2d1e71fbd7a2571e01412339de534ae2fcef2
Timestamp: 1703164517 Timestamp [UCT]: 2023-12-21 13:15:17 Age [y:d:h:m:s]: 01:125:19:10:42
Block: 917975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351055 RingCT/type: yes/0
Extra: 019655e6561cc077a87295cfaabcd2d1e71fbd7a2571e01412339de534ae2fcef202110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bdcb07070b65a234349be4c50b9dfab7ea6dd9f40d418b36abcefa755ba6dcb 0.600000000000 1375609 of 15

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": 917985, "vin": [ { "gen": { "height": 917975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bdcb07070b65a234349be4c50b9dfab7ea6dd9f40d418b36abcefa755ba6dcb" } } ], "extra": [ 1, 150, 85, 230, 86, 28, 192, 119, 168, 114, 149, 207, 170, 188, 210, 209, 231, 31, 189, 122, 37, 113, 224, 20, 18, 51, 157, 229, 52, 174, 47, 206, 242, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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