Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442dd92526cd8e4f527410a2c339b15ab8b18f2e5c45b64e60e978e58a3ed809

Tx prefix hash: 736649fc73cb3cc928137cb7a8411a505e8866f831d47b6479fff438aa49f3e6
Tx public key: 0b775542bbb4c15cbf3e983703ba2a1eabeaffae61c90f754e86ed7f6433b132
Timestamp: 1718337749 Timestamp [UCT]: 2024-06-14 04:02:29 Age [y:d:h:m:s]: 01:146:09:48:03
Block: 1043779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363190 RingCT/type: yes/0
Extra: 010b775542bbb4c15cbf3e983703ba2a1eabeaffae61c90f754e86ed7f6433b1320211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a96eb72f5de2d9122f969240e426fc7109269dc45e6eddf661b40bdd2628d63 0.600000000000 1512938 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": 1043789, "vin": [ { "gen": { "height": 1043779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a96eb72f5de2d9122f969240e426fc7109269dc45e6eddf661b40bdd2628d63" } } ], "extra": [ 1, 11, 119, 85, 66, 187, 180, 193, 92, 191, 62, 152, 55, 3, 186, 42, 30, 171, 234, 255, 174, 97, 201, 15, 117, 78, 134, 237, 127, 100, 51, 177, 50, 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