Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cbe2c2578cf5dc6896a2918a68c58c0a6e69ae1fa98ca3d65cbca499d890e8f

Tx prefix hash: e98c0d0817e1d705f5228e324acdf24852be22f6987356d7e6b8338aa2e1231d
Tx public key: 48c94574c11ae4881e1b2e3a68cff5248ba2ab6a044ccbf57597843bf9a4fce7
Timestamp: 1705206784 Timestamp [UCT]: 2024-01-14 04:33:04 Age [y:d:h:m:s]: 01:355:07:18:06
Block: 934891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512842 RingCT/type: yes/0
Extra: 0148c94574c11ae4881e1b2e3a68cff5248ba2ab6a044ccbf57597843bf9a4fce70211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61bcc8213ab50acbb8ca80d26378a1be60139e406a40083c0eecddef819b5758 0.600000000000 1392907 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": 934901, "vin": [ { "gen": { "height": 934891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61bcc8213ab50acbb8ca80d26378a1be60139e406a40083c0eecddef819b5758" } } ], "extra": [ 1, 72, 201, 69, 116, 193, 26, 228, 136, 30, 27, 46, 58, 104, 207, 245, 36, 139, 162, 171, 106, 4, 76, 203, 245, 117, 151, 132, 59, 249, 164, 252, 231, 2, 17, 0, 0, 0, 16, 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