Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac29f4a98ce98f9e4ee34bab278247faaf7e17f46d0bb2f8a41b2fb6921bb6f

Tx prefix hash: 16efcbddb56edc964a2690c1845e8238156c3529ccf7103bb194f0a5b947eb6a
Tx public key: 221da50e1305f383fb1d977471e0c4874b46ac5c4889b9266ed4e33679aaad7b
Timestamp: 1702687615 Timestamp [UCT]: 2023-12-16 00:46:55 Age [y:d:h:m:s]: 01:027:02:34:08
Block: 914022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280723 RingCT/type: yes/0
Extra: 01221da50e1305f383fb1d977471e0c4874b46ac5c4889b9266ed4e33679aaad7b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02fc357b807353b2bfabecb63c3d5abf81a1ca9acc948d086d48dc0e5032979d 0.600000000000 1371304 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": 914032, "vin": [ { "gen": { "height": 914022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02fc357b807353b2bfabecb63c3d5abf81a1ca9acc948d086d48dc0e5032979d" } } ], "extra": [ 1, 34, 29, 165, 14, 19, 5, 243, 131, 251, 29, 151, 116, 113, 224, 196, 135, 75, 70, 172, 92, 72, 137, 185, 38, 110, 212, 227, 54, 121, 170, 173, 123, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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