Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a9ec4886cf80b9137fc8b6c05f5b4cd7fb778965d4efdb2f6572f5e01c6b44f

Tx prefix hash: 67a02b31de50b9ac23b0f3b43411afa4ed5e348c640e21d8c3e215f1db01bd7c
Tx public key: e93bef81134d1e52c564072ee62f81be54543dd103fd2570564469dd846e54dc
Timestamp: 1685584050 Timestamp [UCT]: 2023-06-01 01:47:30 Age [y:d:h:m:s]: 01:333:13:35:22
Block: 772479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499626 RingCT/type: yes/0
Extra: 01e93bef81134d1e52c564072ee62f81be54543dd103fd2570564469dd846e54dc021100000002faf35c9c000000000000000000

1 output(s) for total of 1.692219019000 dcy

stealth address amount amount idx
00: 5ed48f49d07b21a7f4caa5fb3e26421408fd8ebae033989c6bff31862661b270 1.692219019000 1221886 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": 772489, "vin": [ { "gen": { "height": 772479 } } ], "vout": [ { "amount": 1692219019, "target": { "key": "5ed48f49d07b21a7f4caa5fb3e26421408fd8ebae033989c6bff31862661b270" } } ], "extra": [ 1, 233, 59, 239, 129, 19, 77, 30, 82, 197, 100, 7, 46, 230, 47, 129, 190, 84, 84, 61, 209, 3, 253, 37, 112, 86, 68, 105, 221, 132, 110, 84, 220, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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