Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60efe822be886b11ed547a40141405ac970e7686d88033d80215c95e71f5ecd

Tx prefix hash: 86927ed7fc95d779451bd2cc3f9292ceb52587f79de912e5a36686b809330982
Tx public key: b9b6110a970a4be50a219afd95419df8f67ea51db5597a49301e3217cb1593b7
Timestamp: 1633607186 Timestamp [UCT]: 2021-10-07 11:46:26 Age [y:d:h:m:s]: 03:054:20:35:22
Block: 348455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816410 RingCT/type: yes/0
Extra: 01b9b6110a970a4be50a219afd95419df8f67ea51db5597a49301e3217cb1593b702110000000cfdc024ec000000000000000000

1 output(s) for total of 42.995634233000 dcy

stealth address amount amount idx
00: 483a19c40a96292165b67a0e3ee4d127a856208e8ae012da731c3a58a908c762 42.995634233000 713565 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": 348465, "vin": [ { "gen": { "height": 348455 } } ], "vout": [ { "amount": 42995634233, "target": { "key": "483a19c40a96292165b67a0e3ee4d127a856208e8ae012da731c3a58a908c762" } } ], "extra": [ 1, 185, 182, 17, 10, 151, 10, 75, 229, 10, 33, 154, 253, 149, 65, 157, 248, 246, 126, 165, 29, 181, 89, 122, 73, 48, 30, 50, 23, 203, 21, 147, 183, 2, 17, 0, 0, 0, 12, 253, 192, 36, 236, 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