Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15924abd2a48abe4e34826cc201fd4b5db61099d921c6bd4bb44f4380be873ff

Tx prefix hash: 6aaf02655bff422821cf3ab2a57fa856e5e84e879b16f7a6e98977aef7a0e9d7
Tx public key: cc00141ae8d43f76974489388b29737e8d4ba2a2c89713bea05fe1c88aada6f4
Timestamp: 1736692009 Timestamp [UCT]: 2025-01-12 14:26:49 Age [y:d:h:m:s]: 00:157:10:08:39
Block: 1195802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112206 RingCT/type: yes/0
Extra: 01cc00141ae8d43f76974489388b29737e8d4ba2a2c89713bea05fe1c88aada6f40211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fae12f0641a97b6ab3ba4c44737bf98f111bc0aaec379533a042b89fb9ae3c32 0.600000000000 1682395 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": 1195812, "vin": [ { "gen": { "height": 1195802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fae12f0641a97b6ab3ba4c44737bf98f111bc0aaec379533a042b89fb9ae3c32" } } ], "extra": [ 1, 204, 0, 20, 26, 232, 212, 63, 118, 151, 68, 137, 56, 139, 41, 115, 126, 141, 75, 162, 162, 200, 151, 19, 190, 160, 95, 225, 200, 138, 173, 166, 244, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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