Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f487aa82030e5a8dd2b95071d2ebae2fe621850da52309254bf3af9cd681643e

Tx prefix hash: aae7f0158878b7fcccb7d878458ae3fee814f6b9572412e77a64680c59774ffc
Tx public key: c562114796431bdd7b51393369eed05c5dc1f2b1d1ffc552a8186fd900ae1c54
Timestamp: 1719407009 Timestamp [UCT]: 2024-06-26 13:03:29 Age [y:d:h:m:s]: 01:138:20:11:44
Block: 1052630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357780 RingCT/type: yes/0
Extra: 01c562114796431bdd7b51393369eed05c5dc1f2b1d1ffc552a8186fd900ae1c540211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21819d2854278c76e0af8c85fa352a1a596fce1c37eec5780d30e5eab85a9894 0.600000000000 1522961 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": 1052640, "vin": [ { "gen": { "height": 1052630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21819d2854278c76e0af8c85fa352a1a596fce1c37eec5780d30e5eab85a9894" } } ], "extra": [ 1, 197, 98, 17, 71, 150, 67, 27, 221, 123, 81, 57, 51, 105, 238, 208, 92, 93, 193, 242, 177, 209, 255, 197, 82, 168, 24, 111, 217, 0, 174, 28, 84, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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