Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c577c89195a127516c09b78007a7e612b369b5aec34c06013cbd6a60f6a7a748

Tx prefix hash: f61b849b754566be1cffa5e991cd7342106ccf1f737351654a8155bd9d9dcc2a
Tx public key: fad1ce651b3142a5c89460e8ba07b8d5b63c88bb6399e3ebb2b35e472f11b8c5
Timestamp: 1709647393 Timestamp [UCT]: 2024-03-05 14:03:13 Age [y:d:h:m:s]: 01:050:17:57:52
Block: 971735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297280 RingCT/type: yes/0
Extra: 01fad1ce651b3142a5c89460e8ba07b8d5b63c88bb6399e3ebb2b35e472f11b8c50211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29f89d9a8b272e81a76756a1b78755ecbe154c98f7073712ccbcc286ba9b1806 0.600000000000 1431636 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": 971745, "vin": [ { "gen": { "height": 971735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f89d9a8b272e81a76756a1b78755ecbe154c98f7073712ccbcc286ba9b1806" } } ], "extra": [ 1, 250, 209, 206, 101, 27, 49, 66, 165, 200, 148, 96, 232, 186, 7, 184, 213, 182, 60, 136, 187, 99, 153, 227, 235, 178, 179, 94, 71, 47, 17, 184, 197, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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