Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 857bd852b0fb8ca9c8ec823c3da18b4a7a95907c9ac0f2edb4bac2cc6000af68

Tx prefix hash: 40ba2c3d42ff2e3f88e7b8c710e99e8b4e3d4fda5bbea953cbe1e529623bb8a0
Tx public key: f8f637e3309810213378396d0a47e052234e9e28b330e0af5a84fb4613b16897
Timestamp: 1727974131 Timestamp [UCT]: 2024-10-03 16:48:51 Age [y:d:h:m:s]: 00:019:14:35:03
Block: 1123668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14008 RingCT/type: yes/0
Extra: 01f8f637e3309810213378396d0a47e052234e9e28b330e0af5a84fb4613b1689702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6830e55bf32df75cc6ca37a4618c880bba87a63532c90a40994b5eda784d114 0.600000000000 1606203 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": 1123678, "vin": [ { "gen": { "height": 1123668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6830e55bf32df75cc6ca37a4618c880bba87a63532c90a40994b5eda784d114" } } ], "extra": [ 1, 248, 246, 55, 227, 48, 152, 16, 33, 51, 120, 57, 109, 10, 71, 224, 82, 35, 78, 158, 40, 179, 48, 224, 175, 90, 132, 251, 70, 19, 177, 104, 151, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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