Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69552e5ddcb5d311e884a55c1603eb8171cbb99936e15cce79f8b6c0a2e1b877

Tx prefix hash: c94dac4c41f7c1d47f13e346aec040d8a238df27a66b7f8207bad29347f5009a
Tx public key: 27fb2401e7e88d36be65749d81f4c137e894324ccd921fcf0bf341a74ed400de
Timestamp: 1693336915 Timestamp [UCT]: 2023-08-29 19:21:55 Age [y:d:h:m:s]: 01:134:00:42:01
Block: 836689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357129 RingCT/type: yes/0
Extra: 0127fb2401e7e88d36be65749d81f4c137e894324ccd921fcf0bf341a74ed400de02110000000d3c9a4d68000000000000000000

1 output(s) for total of 1.036816961000 dcy

stealth address amount amount idx
00: 79694760dc2504d5eb22524799bf48570770d612bbf218705d83b962b47ec13c 1.036816961000 1289281 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": 836699, "vin": [ { "gen": { "height": 836689 } } ], "vout": [ { "amount": 1036816961, "target": { "key": "79694760dc2504d5eb22524799bf48570770d612bbf218705d83b962b47ec13c" } } ], "extra": [ 1, 39, 251, 36, 1, 231, 232, 141, 54, 190, 101, 116, 157, 129, 244, 193, 55, 232, 148, 50, 76, 205, 146, 31, 207, 11, 243, 65, 167, 78, 212, 0, 222, 2, 17, 0, 0, 0, 13, 60, 154, 77, 104, 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