Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c9611b16e42b15a91332218542d6a0caa683eb007c9cca0e2a2b8c7b2c692e5

Tx prefix hash: 8a710950b9a2730eb366da2dcf6e644821c9b73bfe42828f1ea75f6616c0bd37
Tx public key: 324af1c4222fc8e36e6fcb109d562cec44519be600c21e81bbf27e6585261f3e
Timestamp: 1704341753 Timestamp [UCT]: 2024-01-04 04:15:53 Age [y:d:h:m:s]: 01:309:12:06:09
Block: 927742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480022 RingCT/type: yes/0
Extra: 01324af1c4222fc8e36e6fcb109d562cec44519be600c21e81bbf27e6585261f3e021100000008bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368a2b4b1098908ebb817d410be97d7d4087a167a8166db8c538ca504db2664c 0.600000000000 1385578 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": 927752, "vin": [ { "gen": { "height": 927742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368a2b4b1098908ebb817d410be97d7d4087a167a8166db8c538ca504db2664c" } } ], "extra": [ 1, 50, 74, 241, 196, 34, 47, 200, 227, 110, 111, 203, 16, 157, 86, 44, 236, 68, 81, 155, 230, 0, 194, 30, 129, 187, 242, 126, 101, 133, 38, 31, 62, 2, 17, 0, 0, 0, 8, 191, 162, 34, 33, 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