Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97f03484e147424c2ba4fa3568cc7e302d68a4b6edc792a4b7c5138f6366f8ad

Tx prefix hash: 3cb02d8a28558de87708d754bec322e545e956bdbbc5c18c39c8f714e422119f
Tx public key: 74d22927acc34fb4f0f6c753e8dba1ecc99570fe0d924a21e82981fdeff57e79
Timestamp: 1736130964 Timestamp [UCT]: 2025-01-06 02:36:04 Age [y:d:h:m:s]: 00:088:18:14:39
Block: 1191161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63207 RingCT/type: yes/0
Extra: 0174d22927acc34fb4f0f6c753e8dba1ecc99570fe0d924a21e82981fdeff57e7902110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0981e415d000300452049b339e96cfde6bc7eec5023310ac752c0348faf9b5fd 0.600000000000 1677684 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": 1191171, "vin": [ { "gen": { "height": 1191161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0981e415d000300452049b339e96cfde6bc7eec5023310ac752c0348faf9b5fd" } } ], "extra": [ 1, 116, 210, 41, 39, 172, 195, 79, 180, 240, 246, 199, 83, 232, 219, 161, 236, 201, 149, 112, 254, 13, 146, 74, 33, 232, 41, 129, 253, 239, 245, 126, 121, 2, 17, 0, 0, 0, 10, 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