Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8caf0a09ceaf708e5d336aa6ed01660cc08d5ef13fa9ee86fd05da469d8afbe4

Tx prefix hash: eebb625a092f73a49a9bd95d71059b1ef7e306aa47d9d8e56fb1df7317c473ce
Tx public key: 92e834cd87ebb2039da16518103c54ca53f6d4e3d069f0039e46c275819c29d8
Timestamp: 1742906358 Timestamp [UCT]: 2025-03-25 12:39:18 Age [y:d:h:m:s]: 00:254:15:26:00
Block: 1246974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179760 RingCT/type: yes/0
Extra: 0192e834cd87ebb2039da16518103c54ca53f6d4e3d069f0039e46c275819c29d8021100000007c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79b94e691e329cc78ac87e08b9a2e3f0009c458f73215c5c6d71808f8898ab6f 0.600000000000 1733975 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": 1246984, "vin": [ { "gen": { "height": 1246974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79b94e691e329cc78ac87e08b9a2e3f0009c458f73215c5c6d71808f8898ab6f" } } ], "extra": [ 1, 146, 232, 52, 205, 135, 235, 178, 3, 157, 161, 101, 24, 16, 60, 84, 202, 83, 246, 212, 227, 208, 105, 240, 3, 158, 70, 194, 117, 129, 156, 41, 216, 2, 17, 0, 0, 0, 7, 198, 116, 9, 88, 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