Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd17b03be590e02e1938320ae2a8f752aae900e733fc6caf6cb1358d1c113064

Tx prefix hash: 0e517a6d62004ca6fbff4e7c11301630dbb640aa52aa949f84315271bbb212bd
Tx public key: 676216840088388dddc1319a4fae81ad9c6e6ca5971cab3b6fd26cbef17d7ace
Timestamp: 1707524012 Timestamp [UCT]: 2024-02-10 00:13:32 Age [y:d:h:m:s]: 01:054:02:02:51
Block: 954107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299703 RingCT/type: yes/0
Extra: 01676216840088388dddc1319a4fae81ad9c6e6ca5971cab3b6fd26cbef17d7ace02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b9c39ff0e8fe4df1c3359ceeb4d4e3d7ab6fd1067dcad01e483063d43ff8d21 0.600000000000 1413381 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": 954117, "vin": [ { "gen": { "height": 954107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b9c39ff0e8fe4df1c3359ceeb4d4e3d7ab6fd1067dcad01e483063d43ff8d21" } } ], "extra": [ 1, 103, 98, 22, 132, 0, 136, 56, 141, 221, 193, 49, 154, 79, 174, 129, 173, 156, 110, 108, 165, 151, 28, 171, 59, 111, 210, 108, 190, 241, 125, 122, 206, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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