Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64210902655ef7ea2c0ac910f5e1da71a656599dc9a901575d1f335df090106c

Tx prefix hash: fb08444d6a62db7e69ae01f8f883c06faf040268f8d6f70347264ff334f45c06
Tx public key: 855ec40b1ab3f927be492dcd1688df4d4d930a7adf8814cd0af8f7cc1784eb99
Timestamp: 1733149581 Timestamp [UCT]: 2024-12-02 14:26:21 Age [y:d:h:m:s]: 00:195:15:36:01
Block: 1166466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139586 RingCT/type: yes/0
Extra: 01855ec40b1ab3f927be492dcd1688df4d4d930a7adf8814cd0af8f7cc1784eb990211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3070b13b52f4b3871304e80bf5c688e194fa5c6cc4524dad304455e6df69231 0.600000000000 1652153 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": 1166476, "vin": [ { "gen": { "height": 1166466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3070b13b52f4b3871304e80bf5c688e194fa5c6cc4524dad304455e6df69231" } } ], "extra": [ 1, 133, 94, 196, 11, 26, 179, 249, 39, 190, 73, 45, 205, 22, 136, 223, 77, 77, 147, 10, 122, 223, 136, 20, 205, 10, 248, 247, 204, 23, 132, 235, 153, 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