Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 409c3e40eedba4b2db869cf2044cc2983d5007dbd8c4353c659a50da5e5c6a8d

Tx prefix hash: 044676ffe7cb381c0610cb5d9bdf966dc6bcd388329f9f8378d319a55be7d307
Tx public key: aea587f5c53daff2043554b6ec06481dc77c99275d272285ab6e54592436ea7e
Timestamp: 1710668507 Timestamp [UCT]: 2024-03-17 09:41:47 Age [y:d:h:m:s]: 01:080:16:40:18
Block: 980210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318682 RingCT/type: yes/0
Extra: 01aea587f5c53daff2043554b6ec06481dc77c99275d272285ab6e54592436ea7e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a2639d2ec364b8f83545797e3f6e921e7ced916da5acf1ad178283c81d05449 0.600000000000 1440275 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": 980220, "vin": [ { "gen": { "height": 980210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a2639d2ec364b8f83545797e3f6e921e7ced916da5acf1ad178283c81d05449" } } ], "extra": [ 1, 174, 165, 135, 245, 197, 61, 175, 242, 4, 53, 84, 182, 236, 6, 72, 29, 199, 124, 153, 39, 93, 39, 34, 133, 171, 110, 84, 89, 36, 54, 234, 126, 2, 17, 0, 0, 0, 6, 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