Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cced2d094dd4d053f4a6c984813edc578a26a08a0c88436d36e4bf00e4798fd

Tx prefix hash: 68537c7ad58410765779fc53b5e3b85f728a0d0dc5086eab8e02c3a256aad1f2
Tx public key: 42670ce3da981ec4a24fafaded118ea628861e4b291a98c406d6bf8c54a844e8
Timestamp: 1708802799 Timestamp [UCT]: 2024-02-24 19:26:39 Age [y:d:h:m:s]: 01:108:17:03:29
Block: 964733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338711 RingCT/type: yes/0
Extra: 0142670ce3da981ec4a24fafaded118ea628861e4b291a98c406d6bf8c54a844e80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 613a7a2ddabedf9d906c47527bd8ed23cc7d1df83fdd6378299bee0bd35fd576 0.600000000000 1424476 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": 964743, "vin": [ { "gen": { "height": 964733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "613a7a2ddabedf9d906c47527bd8ed23cc7d1df83fdd6378299bee0bd35fd576" } } ], "extra": [ 1, 66, 103, 12, 227, 218, 152, 30, 196, 162, 79, 175, 173, 237, 17, 142, 166, 40, 134, 30, 75, 41, 26, 152, 196, 6, 214, 191, 140, 84, 168, 68, 232, 2, 17, 0, 0, 0, 1, 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