Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8433908378de786982fcf6f145e48f21e9e9efa643d0acdc8a736a8b27413e92

Tx prefix hash: c331652a38239d4352522029db2b1159d8dad7dee5296fb674ab54336de74788
Tx public key: c24c5e828b69d89685dc05e6b9a45d5dfa69a5c70f1c2d2e0c555ad15637e192
Timestamp: 1699138646 Timestamp [UCT]: 2023-11-04 22:57:26 Age [y:d:h:m:s]: 01:133:13:33:28
Block: 884859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356410 RingCT/type: yes/0
Extra: 01c24c5e828b69d89685dc05e6b9a45d5dfa69a5c70f1c2d2e0c555ad15637e19202110000000a33af99f4000000000000000000

1 output(s) for total of 0.717951019000 dcy

stealth address amount amount idx
00: 6cbba46140f668b25bd6798af9011358338496938d3d7af440716f163d2aa568 0.717951019000 1340608 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": 884869, "vin": [ { "gen": { "height": 884859 } } ], "vout": [ { "amount": 717951019, "target": { "key": "6cbba46140f668b25bd6798af9011358338496938d3d7af440716f163d2aa568" } } ], "extra": [ 1, 194, 76, 94, 130, 139, 105, 216, 150, 133, 220, 5, 230, 185, 164, 93, 93, 250, 105, 165, 199, 15, 28, 45, 46, 12, 85, 90, 209, 86, 55, 225, 146, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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