Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 517fac704ea345c0de80eea5eeaf6397a4e9410be2aad84889c9479e9ea205bc

Tx prefix hash: d47a5043b3a4b32c49d4a576891ec5769fd1a116772635dfd898cb117f7a6061
Tx public key: 6dd9d95faa7c7349ea09223b05caa666ccc87eb5de2b8546706a3a025d26a043
Timestamp: 1723175837 Timestamp [UCT]: 2024-08-09 03:57:17 Age [y:d:h:m:s]: 01:090:07:48:45
Block: 1083881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323036 RingCT/type: yes/0
Extra: 016dd9d95faa7c7349ea09223b05caa666ccc87eb5de2b8546706a3a025d26a043021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3d554d449dc7f9f74bf40f5d22181a8bd28a065249ba78191eb9f6ebef61c3a 0.600000000000 1557960 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": 1083891, "vin": [ { "gen": { "height": 1083881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3d554d449dc7f9f74bf40f5d22181a8bd28a065249ba78191eb9f6ebef61c3a" } } ], "extra": [ 1, 109, 217, 217, 95, 170, 124, 115, 73, 234, 9, 34, 59, 5, 202, 166, 102, 204, 200, 126, 181, 222, 43, 133, 70, 112, 106, 58, 2, 93, 38, 160, 67, 2, 17, 0, 0, 0, 1, 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