Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d34602bb47a96089a6b98771578ea5ae9ae2f827dd92459a6134726eadcca755

Tx prefix hash: 860f52b3b48c4e506baa5fa43ed1afe3e5cb95e3b83b87cd61715e7356e77160
Tx public key: ca720c7cb646ae8c1746bca19ce85010504cbf0c3ca2fedbc181cbf2c824965e
Timestamp: 1707600785 Timestamp [UCT]: 2024-02-10 21:33:05 Age [y:d:h:m:s]: 01:016:22:01:57
Block: 954753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273111 RingCT/type: yes/0
Extra: 01ca720c7cb646ae8c1746bca19ce85010504cbf0c3ca2fedbc181cbf2c824965e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5b6c1c0d1dbb65a4e2cbfcdb209dbddcca9f98ca99c71c007c3b8ee97e6c9f 0.600000000000 1414035 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": 954763, "vin": [ { "gen": { "height": 954753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5b6c1c0d1dbb65a4e2cbfcdb209dbddcca9f98ca99c71c007c3b8ee97e6c9f" } } ], "extra": [ 1, 202, 114, 12, 124, 182, 70, 174, 140, 23, 70, 188, 161, 156, 232, 80, 16, 80, 76, 191, 12, 60, 162, 254, 219, 193, 129, 203, 242, 200, 36, 150, 94, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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