Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcda664eeea088f53c5692c9b001ba31b8e5ea27ec7a44bddb46c2d103bce2cd

Tx prefix hash: 43503c11872be64b242b032c2f2ab495e727a75a3eb49507e8a54dca373dd0ae
Tx public key: af9bdfb7a73ba4581b0dccae17896865474065c7de5ad379a6fd57b8b02b5d42
Timestamp: 1724690549 Timestamp [UCT]: 2024-08-26 16:42:29 Age [y:d:h:m:s]: 00:294:15:01:30
Block: 1096436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210369 RingCT/type: yes/0
Extra: 01af9bdfb7a73ba4581b0dccae17896865474065c7de5ad379a6fd57b8b02b5d42021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71cbfd912e32a9144c16ae6e901339ccc7c73989518a95897c997f65363bb973 0.600000000000 1571625 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": 1096446, "vin": [ { "gen": { "height": 1096436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71cbfd912e32a9144c16ae6e901339ccc7c73989518a95897c997f65363bb973" } } ], "extra": [ 1, 175, 155, 223, 183, 167, 59, 164, 88, 27, 13, 204, 174, 23, 137, 104, 101, 71, 64, 101, 199, 222, 90, 211, 121, 166, 253, 87, 184, 176, 43, 93, 66, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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