Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b66f4d49d7d3d492cde9545abda39614561c45631115ab50371ee080217071

Tx prefix hash: bf6316b7a1da03273638c7f2df12898aae2aad02d579082b1df357f51215aaac
Tx public key: f2ec57ad2cd39cc9b2cb1b5c7fef672d848a05dc8a8432f4223fa8f35d731ba9
Timestamp: 1713329691 Timestamp [UCT]: 2024-04-17 04:54:51 Age [y:d:h:m:s]: 01:243:22:50:58
Block: 1002237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433065 RingCT/type: yes/0
Extra: 01f2ec57ad2cd39cc9b2cb1b5c7fef672d848a05dc8a8432f4223fa8f35d731ba90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1f1721364779794d023d3ad80c54edf9c0198deb827937ed355ece5d4e2c2a 0.600000000000 1462753 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": 1002247, "vin": [ { "gen": { "height": 1002237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1f1721364779794d023d3ad80c54edf9c0198deb827937ed355ece5d4e2c2a" } } ], "extra": [ 1, 242, 236, 87, 173, 44, 211, 156, 201, 178, 203, 27, 92, 127, 239, 103, 45, 132, 138, 5, 220, 138, 132, 50, 244, 34, 63, 168, 243, 93, 115, 27, 169, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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