Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd8a232493eebc2ae7c058fa372c85b6c8536aeda2dcce81192ed0f9cee3e509

Tx prefix hash: bb5cbf549bf1fdae850e7af932cbae0cd374938c9a03b2218dda7337c27c22ab
Tx public key: 478de0fbe06396dff9286e2838b4b51256a69677c51b086d775392c5133193aa
Timestamp: 1714076160 Timestamp [UCT]: 2024-04-25 20:16:00 Age [y:d:h:m:s]: 01:016:22:08:15
Block: 1008436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273043 RingCT/type: yes/0
Extra: 01478de0fbe06396dff9286e2838b4b51256a69677c51b086d775392c5133193aa02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ded951b64a2e4d26a8e538505c28eccb5bc266b99603b174fcc7a1d3f2900eb 0.600000000000 1469906 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": 1008446, "vin": [ { "gen": { "height": 1008436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ded951b64a2e4d26a8e538505c28eccb5bc266b99603b174fcc7a1d3f2900eb" } } ], "extra": [ 1, 71, 141, 224, 251, 224, 99, 150, 223, 249, 40, 110, 40, 56, 180, 181, 18, 86, 166, 150, 119, 197, 27, 8, 109, 119, 83, 146, 197, 19, 49, 147, 170, 2, 17, 0, 0, 0, 3, 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