Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac26cfe31bbce1a32691e5b47c9fbf146c3d2cda8b07db18a65dcd137e65b4d5

Tx prefix hash: d340061debd618ff7600105ed223c0e5418fa01680b9a85fd8c67773462415f1
Tx public key: f248dbfb4a67773bd40fd0c727dc10da40cb002cdea05a73b6423fa5832eb8f8
Timestamp: 1710292505 Timestamp [UCT]: 2024-03-13 01:15:05 Age [y:d:h:m:s]: 01:023:10:23:48
Block: 977085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277734 RingCT/type: yes/0
Extra: 01f248dbfb4a67773bd40fd0c727dc10da40cb002cdea05a73b6423fa5832eb8f80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c4520661f2e745deb840eea60472e2c77456df2b7b495434edf4f4152ac527c 0.600000000000 1437086 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": 977095, "vin": [ { "gen": { "height": 977085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c4520661f2e745deb840eea60472e2c77456df2b7b495434edf4f4152ac527c" } } ], "extra": [ 1, 242, 72, 219, 251, 74, 103, 119, 59, 212, 15, 208, 199, 39, 220, 16, 218, 64, 203, 0, 44, 222, 160, 90, 115, 182, 66, 63, 165, 131, 46, 184, 248, 2, 17, 0, 0, 0, 2, 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