Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71be1c38407a17999320ae1f21563b7c77b2e411a9b5bcb0c2e2d68bd7d21bad

Tx prefix hash: 505e8ea19ae02ea0735085afdca936ae26444d136216ffaeacecfdcc99260d5b
Tx public key: ccd5e5f730518d62f3ee4b4ac3f2417ee2525df2b75a2ce65a272d97fb417491
Timestamp: 1708862716 Timestamp [UCT]: 2024-02-25 12:05:16 Age [y:d:h:m:s]: 01:102:23:01:31
Block: 965230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334641 RingCT/type: yes/0
Extra: 01ccd5e5f730518d62f3ee4b4ac3f2417ee2525df2b75a2ce65a272d97fb4174910211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 417cb525a1fbd81fe2d4e1622a47635cfd04246a0c80b0d0aef5cdc0ac7697c0 0.600000000000 1424979 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": 965240, "vin": [ { "gen": { "height": 965230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "417cb525a1fbd81fe2d4e1622a47635cfd04246a0c80b0d0aef5cdc0ac7697c0" } } ], "extra": [ 1, 204, 213, 229, 247, 48, 81, 141, 98, 243, 238, 75, 74, 195, 242, 65, 126, 226, 82, 93, 242, 183, 90, 44, 230, 90, 39, 45, 151, 251, 65, 116, 145, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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