Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a64d3ee09a20a533cbfedec9d3cd44dd66df68b4e69c6048b9fd2af1d00635

Tx prefix hash: d72c26a16c21a16c3f1063fad5e1af224e6f22896dc04b69abb79dbb765a842a
Tx public key: 539d6b7d47477a152b90a63cfb9826780b0e84cc1e41d96686d8433e289e7329
Timestamp: 1646055613 Timestamp [UCT]: 2022-02-28 13:40:13 Age [y:d:h:m:s]: 02:275:17:47:25
Block: 448367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716466 RingCT/type: yes/0
Extra: 01539d6b7d47477a152b90a63cfb9826780b0e84cc1e41d96686d8433e289e732902110000001ac9067537000000000000000000

1 output(s) for total of 20.062242683000 dcy

stealth address amount amount idx
00: d35f63654b96990ae44892eaa4c93eaa54e69c1f6b080905bd5e115b6a08bf68 20.062242683000 862718 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": 448377, "vin": [ { "gen": { "height": 448367 } } ], "vout": [ { "amount": 20062242683, "target": { "key": "d35f63654b96990ae44892eaa4c93eaa54e69c1f6b080905bd5e115b6a08bf68" } } ], "extra": [ 1, 83, 157, 107, 125, 71, 71, 122, 21, 43, 144, 166, 60, 251, 152, 38, 120, 11, 14, 132, 204, 30, 65, 217, 102, 134, 216, 67, 62, 40, 158, 115, 41, 2, 17, 0, 0, 0, 26, 201, 6, 117, 55, 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