Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02fbc0db0afe361e65d4184ddc41bf2f1b24be23643ee4bd4dfe4146bde95421

Tx prefix hash: 55c4b4133770faeec72b882d33e37f50e9d2b2414eb832246162a67f6f47bef9
Tx public key: d9c7854abe8fb7e8fb53a112b47db14932c6bd998d64cc23ced0aa9e5263b8f6
Timestamp: 1736497282 Timestamp [UCT]: 2025-01-10 08:21:22 Age [y:d:h:m:s]: 00:088:05:33:12
Block: 1194178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62846 RingCT/type: yes/0
Extra: 01d9c7854abe8fb7e8fb53a112b47db14932c6bd998d64cc23ced0aa9e5263b8f60211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0726c8714d1c7d1bf0b33b12352ef55332a19790bebc2454cb63bac631ee15f0 0.600000000000 1680745 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": 1194188, "vin": [ { "gen": { "height": 1194178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0726c8714d1c7d1bf0b33b12352ef55332a19790bebc2454cb63bac631ee15f0" } } ], "extra": [ 1, 217, 199, 133, 74, 190, 143, 183, 232, 251, 83, 161, 18, 180, 125, 177, 73, 50, 198, 189, 153, 141, 100, 204, 35, 206, 208, 170, 158, 82, 99, 184, 246, 2, 17, 0, 0, 0, 7, 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