Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 120d96c9704877c6368bf95536f96d40153207e6a2997b784bb8e299fc263800

Tx prefix hash: 69f2bdea6d9b6af94085b2f9a275fc2612d91bfaba290bcd34da74117e8b5afe
Tx public key: a5b783f9041b021a5a89b1c0c74555e5e78edb1bf4ca30c8f06aa3e8a2a4242f
Timestamp: 1624537055 Timestamp [UCT]: 2021-06-24 12:17:35 Age [y:d:h:m:s]: 03:144:13:52:42
Block: 283458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870465 RingCT/type: yes/0
Extra: 01a5b783f9041b021a5a89b1c0c74555e5e78edb1bf4ca30c8f06aa3e8a2a4242f02110000020f3525d189000000000000000000

1 output(s) for total of 70.597039859000 dcy

stealth address amount amount idx
00: 7573fde3ffcb4cbddaeea1654c2a1554b0b5002829deb6ecc0e2e4780b846458 70.597039859000 593467 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": 283468, "vin": [ { "gen": { "height": 283458 } } ], "vout": [ { "amount": 70597039859, "target": { "key": "7573fde3ffcb4cbddaeea1654c2a1554b0b5002829deb6ecc0e2e4780b846458" } } ], "extra": [ 1, 165, 183, 131, 249, 4, 27, 2, 26, 90, 137, 177, 192, 199, 69, 85, 229, 231, 142, 219, 27, 244, 202, 48, 200, 240, 106, 163, 232, 162, 164, 36, 47, 2, 17, 0, 0, 2, 15, 53, 37, 209, 137, 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