Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09ebab72a59f2e81375c3f254f1a0b0895f88e59daf85bdbff7e498bf328b6d4

Tx prefix hash: ada85e77817ed305cc2aedb7a25c68fba23ed7eb3a813e1d0c0c1818176375e8
Tx public key: 82caa1eb2aa580d4c36eb6eed9e70b141d1b8698a000933b1fe56b6f8f4a9d95
Timestamp: 1714363354 Timestamp [UCT]: 2024-04-29 04:02:34 Age [y:d:h:m:s]: 00:340:16:17:45
Block: 1010817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243532 RingCT/type: yes/0
Extra: 0182caa1eb2aa580d4c36eb6eed9e70b141d1b8698a000933b1fe56b6f8f4a9d950211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc8a12b01452417d2acf30133944570c3ef3e3cb9d77c245d3dfa8e156bc668d 0.600000000000 1472875 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": 1010827, "vin": [ { "gen": { "height": 1010817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc8a12b01452417d2acf30133944570c3ef3e3cb9d77c245d3dfa8e156bc668d" } } ], "extra": [ 1, 130, 202, 161, 235, 42, 165, 128, 212, 195, 110, 182, 238, 217, 231, 11, 20, 29, 27, 134, 152, 160, 0, 147, 59, 31, 229, 107, 111, 143, 74, 157, 149, 2, 17, 0, 0, 0, 1, 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