Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d662bafda35f0c29a22df9c2af758be3fe0b84e04143df02dbd858cb452d0270

Tx prefix hash: e79254eccdbfaa618509235c095b6a0b353b3bb41ace8b0bc41266cac5c8ffc9
Tx public key: f4d0a7939a98e761a10d773272cefdd235c361bf061d6a180389e72d0efde9f3
Timestamp: 1722224288 Timestamp [UCT]: 2024-07-29 03:38:08 Age [y:d:h:m:s]: 00:256:03:45:26
Block: 1075998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182986 RingCT/type: yes/0
Extra: 01f4d0a7939a98e761a10d773272cefdd235c361bf061d6a180389e72d0efde9f3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4340e18c2ef4154ba7d8b9fc59024bc7f87d1cef286ccc5d0d4fea03ab7f9d5 0.600000000000 1548533 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": 1076008, "vin": [ { "gen": { "height": 1075998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4340e18c2ef4154ba7d8b9fc59024bc7f87d1cef286ccc5d0d4fea03ab7f9d5" } } ], "extra": [ 1, 244, 208, 167, 147, 154, 152, 231, 97, 161, 13, 119, 50, 114, 206, 253, 210, 53, 195, 97, 191, 6, 29, 106, 24, 3, 137, 231, 45, 14, 253, 233, 243, 2, 17, 0, 0, 0, 4, 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