Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef2c62aca325eadf55601838ac90838d699e4c43f656b3c4d4a7e129fd87e7b1

Tx prefix hash: 3bc68371da785823966129e68cb15e2fe8349b4545416c6ee5da9ebacb04d2b2
Tx public key: 76efde7441aff19f1fcffba32012b1c5a03da53033f70f611e894d7652b6438a
Timestamp: 1581797950 Timestamp [UCT]: 2020-02-15 20:19:10 Age [y:d:h:m:s]: 05:109:03:50:37
Block: 65560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1231122 RingCT/type: yes/0
Extra: 0176efde7441aff19f1fcffba32012b1c5a03da53033f70f611e894d7652b6438a02110000001ed81c26c0000000000000000000

1 output(s) for total of 372.201772783000 dcy

stealth address amount amount idx
00: 5b83f34e59e3cf6b2badd9eeab4bdc1c249e6bbfcb24705071929589efc8479a 372.201772783000 120975 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": 65570, "vin": [ { "gen": { "height": 65560 } } ], "vout": [ { "amount": 372201772783, "target": { "key": "5b83f34e59e3cf6b2badd9eeab4bdc1c249e6bbfcb24705071929589efc8479a" } } ], "extra": [ 1, 118, 239, 222, 116, 65, 175, 241, 159, 31, 207, 251, 163, 32, 18, 177, 197, 160, 61, 165, 48, 51, 247, 15, 97, 30, 137, 77, 118, 82, 182, 67, 138, 2, 17, 0, 0, 0, 30, 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