Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 028f429befa4e4f9b15fee9878ab43ecdfb7631eaf51e8282f6ecfe5cab5962a

Tx prefix hash: 074c7c0cd0a778706e3277ecaece07331c66a6be27bf5fb3fd865b2c58e2b5ba
Tx public key: fae365b182c6951194c641dc14c3140c0ca2df28a613c05200a2535067a96011
Timestamp: 1705786566 Timestamp [UCT]: 2024-01-20 21:36:06 Age [y:d:h:m:s]: 01:036:01:54:28
Block: 939684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286861 RingCT/type: yes/0
Extra: 01fae365b182c6951194c641dc14c3140c0ca2df28a613c05200a2535067a960110211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f2aad8b3b04006912e2fe177447c92f241cb9b60cfc2e7f4aefceb290517d0b 0.600000000000 1397796 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": 939694, "vin": [ { "gen": { "height": 939684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f2aad8b3b04006912e2fe177447c92f241cb9b60cfc2e7f4aefceb290517d0b" } } ], "extra": [ 1, 250, 227, 101, 177, 130, 198, 149, 17, 148, 198, 65, 220, 20, 195, 20, 12, 12, 162, 223, 40, 166, 19, 192, 82, 0, 162, 83, 80, 103, 169, 96, 17, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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