Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e6adfc92f8c263784e947b3f273045c6e971b9be3dff5fb418e5e1fab4f783

Tx prefix hash: 0234ff85656011ba38ee8a3478184ac47db8d4164807e791b3b36d0b08807e76
Tx public key: f8a92303e434b9092362f3f20da9520d5a1e93f0f6edae097d74d2c9085f2f55
Timestamp: 1708253732 Timestamp [UCT]: 2024-02-18 10:55:32 Age [y:d:h:m:s]: 01:036:03:49:00
Block: 960175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286860 RingCT/type: yes/0
Extra: 01f8a92303e434b9092362f3f20da9520d5a1e93f0f6edae097d74d2c9085f2f550211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce89cb0bbc4aa0658e019b3dd78c9037bc91facdead352e5b7882c679dafe0a3 0.600000000000 1419736 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": 960185, "vin": [ { "gen": { "height": 960175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce89cb0bbc4aa0658e019b3dd78c9037bc91facdead352e5b7882c679dafe0a3" } } ], "extra": [ 1, 248, 169, 35, 3, 228, 52, 185, 9, 35, 98, 243, 242, 13, 169, 82, 13, 90, 30, 147, 240, 246, 237, 174, 9, 125, 116, 210, 201, 8, 95, 47, 85, 2, 17, 0, 0, 0, 4, 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