Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13356c63ca74ca003cabe5b20425f7dfcce737725cd607de04f275ce676b55a8

Tx prefix hash: 689c37b4b79e4bfb5941b1ec424059b047aa52b2b47e4364fef955368fe0b138
Tx public key: 4c8f13f73db56aca6f90ed031519d9f9ae9e7a3f9e9d53202b84b9a053d92893
Timestamp: 1734765736 Timestamp [UCT]: 2024-12-21 07:22:16 Age [y:d:h:m:s]: 00:014:22:46:21
Block: 1179874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10678 RingCT/type: yes/0
Extra: 014c8f13f73db56aca6f90ed031519d9f9ae9e7a3f9e9d53202b84b9a053d928930211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e359890e9a05c642492570d1adad54277f6f66e17455333a56fd03f89edc16cc 0.600000000000 1666275 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": 1179884, "vin": [ { "gen": { "height": 1179874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e359890e9a05c642492570d1adad54277f6f66e17455333a56fd03f89edc16cc" } } ], "extra": [ 1, 76, 143, 19, 247, 61, 181, 106, 202, 111, 144, 237, 3, 21, 25, 217, 249, 174, 158, 122, 63, 158, 157, 83, 32, 43, 132, 185, 160, 83, 217, 40, 147, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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