Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0669a15052da7c172656be8b0da78f0a552df86e7a7f888798dcdfbcae8f3893

Tx prefix hash: 509a171f4bacf004df011241125952a483d9c9b16077c5e3b0b62447e94a028e
Tx public key: 00729ed74486ae802f9714ffc2b3a5ffc182c808112570e8ecefea53a1c72624
Timestamp: 1726474645 Timestamp [UCT]: 2024-09-16 08:17:25 Age [y:d:h:m:s]: 00:128:21:17:00
Block: 1111239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92123 RingCT/type: yes/0
Extra: 0100729ed74486ae802f9714ffc2b3a5ffc182c808112570e8ecefea53a1c7262402110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b07e0ac2abe6ae65c2ce5f2ebaca3d8f6bf9efe9986b90f3de1ce36143c71c 0.600000000000 1590126 of 15

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": 1111249, "vin": [ { "gen": { "height": 1111239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b07e0ac2abe6ae65c2ce5f2ebaca3d8f6bf9efe9986b90f3de1ce36143c71c" } } ], "extra": [ 1, 0, 114, 158, 215, 68, 134, 174, 128, 47, 151, 20, 255, 194, 179, 165, 255, 193, 130, 200, 8, 17, 37, 112, 232, 236, 239, 234, 83, 161, 199, 38, 36, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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