Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e6597e1254e8b8ed1451516a6f8f4ee009e2ec8c7b32e0676cc110b0d8cfd9

Tx prefix hash: 7bd18879ddd3cbc914b30400562c4055297160b69db49624dfbb0f5d165dfce4
Tx public key: 644a71aec1ca078199802e683c19af0296d9e0fb71687d0dcab192f6d7aaca6d
Timestamp: 1712703548 Timestamp [UCT]: 2024-04-09 22:59:08 Age [y:d:h:m:s]: 01:034:05:43:32
Block: 997045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285467 RingCT/type: yes/0
Extra: 01644a71aec1ca078199802e683c19af0296d9e0fb71687d0dcab192f6d7aaca6d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39a09401ac4ff780f06d7d2423f872fa087a6c662457e7079092db7296a7b36f 0.600000000000 1457473 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": 997055, "vin": [ { "gen": { "height": 997045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39a09401ac4ff780f06d7d2423f872fa087a6c662457e7079092db7296a7b36f" } } ], "extra": [ 1, 100, 74, 113, 174, 193, 202, 7, 129, 153, 128, 46, 104, 60, 25, 175, 2, 150, 217, 224, 251, 113, 104, 125, 13, 202, 177, 146, 246, 215, 170, 202, 109, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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