Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e6da38c507a8a2c179bfd0c0ed7ead12dea6472a375c39cec51f3d024ffb7ba

Tx prefix hash: 9384ff9543c580668f2348b46f3292cdf738e9bcd96bcb2a80eb666225795b25
Tx public key: 303bd4757b5a5d30b5a8a30612723c6df6b6daad47856a8e1e97094981217e00
Timestamp: 1716536731 Timestamp [UCT]: 2024-05-24 07:45:31 Age [y:d:h:m:s]: 00:243:18:44:26
Block: 1028855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174411 RingCT/type: yes/0
Extra: 01303bd4757b5a5d30b5a8a30612723c6df6b6daad47856a8e1e97094981217e0002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aaf8cdc7f86571720e53f7ce6aaf3f449fea72d2541757563d742fff21a428c 0.600000000000 1496854 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": 1028865, "vin": [ { "gen": { "height": 1028855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aaf8cdc7f86571720e53f7ce6aaf3f449fea72d2541757563d742fff21a428c" } } ], "extra": [ 1, 48, 59, 212, 117, 123, 90, 93, 48, 181, 168, 163, 6, 18, 114, 60, 109, 246, 182, 218, 173, 71, 133, 106, 142, 30, 151, 9, 73, 129, 33, 126, 0, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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