Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf924338bd65ffcc28ddc09e4d093d95936b9971bc7ba354e60d9ab8311de00

Tx prefix hash: dc4bd8c44963459f773bd24d7971a6aab3bca704ab7219e1d935c5b1715c51e6
Tx public key: d3661cdc67d9b9af7f7247c3419fd37305fa92e8ae3c34b99e07701aa27fc53c
Timestamp: 1696177164 Timestamp [UCT]: 2023-10-01 16:19:24 Age [y:d:h:m:s]: 01:185:14:11:48
Block: 860257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393690 RingCT/type: yes/0
Extra: 01d3661cdc67d9b9af7f7247c3419fd37305fa92e8ae3c34b99e07701aa27fc53c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.866186660000 dcy

stealth address amount amount idx
00: da60f8b263b9ad78b826522e35dea8e9327112fe4aa4c8c0abc14a3812f9d1e9 0.866186660000 1314533 of 0

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": 860267, "vin": [ { "gen": { "height": 860257 } } ], "vout": [ { "amount": 866186660, "target": { "key": "da60f8b263b9ad78b826522e35dea8e9327112fe4aa4c8c0abc14a3812f9d1e9" } } ], "extra": [ 1, 211, 102, 28, 220, 103, 217, 185, 175, 127, 114, 71, 195, 65, 159, 211, 115, 5, 250, 146, 232, 174, 60, 52, 185, 158, 7, 112, 26, 162, 127, 197, 60, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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