Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec70c6e1a51b4b50d2b9487701bd8868c2384d796a6f664b80683b977092eb68

Tx prefix hash: 2654cfd54e7b8f0c00841cc416dd9d2d75ba945266f5f381052adfdb99ac2694
Tx public key: 002da59a3bcd25cd5acbed3853e474f3e53a5d39d1b92f8945bdfa0d258ed039
Timestamp: 1710866008 Timestamp [UCT]: 2024-03-19 16:33:28 Age [y:d:h:m:s]: 01:006:06:38:31
Block: 981854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265433 RingCT/type: yes/0
Extra: 01002da59a3bcd25cd5acbed3853e474f3e53a5d39d1b92f8945bdfa0d258ed03902110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c03e761ce41d26ff53ccdb7cb7fc8af5dea040a3bf1a1a5985d5b19bbab2dc 0.600000000000 1441953 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": 981864, "vin": [ { "gen": { "height": 981854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c03e761ce41d26ff53ccdb7cb7fc8af5dea040a3bf1a1a5985d5b19bbab2dc" } } ], "extra": [ 1, 0, 45, 165, 154, 59, 205, 37, 205, 90, 203, 237, 56, 83, 228, 116, 243, 229, 58, 93, 57, 209, 185, 47, 137, 69, 189, 250, 13, 37, 142, 208, 57, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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