Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56774e018da5a71d6b0101ca1ccf706bd8715f15eb96c817d8ca82075a1b948f

Tx prefix hash: 96af5e74ede5024abf491aa14a72589dd363df7692df534331f2a90fd6fb61db
Tx public key: f121aeca271b78df7724b810d1ad79c95fa0078c2701a08b1d3bf81a615069f0
Timestamp: 1707682083 Timestamp [UCT]: 2024-02-11 20:08:03 Age [y:d:h:m:s]: 01:062:07:41:54
Block: 955429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305610 RingCT/type: yes/0
Extra: 01f121aeca271b78df7724b810d1ad79c95fa0078c2701a08b1d3bf81a615069f00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b0698fcab8fd32f71bcf72eddda7fe6332031ea7d1b6bd951b9d55619b64820 0.600000000000 1414717 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": 955439, "vin": [ { "gen": { "height": 955429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b0698fcab8fd32f71bcf72eddda7fe6332031ea7d1b6bd951b9d55619b64820" } } ], "extra": [ 1, 241, 33, 174, 202, 39, 27, 120, 223, 119, 36, 184, 16, 209, 173, 121, 201, 95, 160, 7, 140, 39, 1, 160, 139, 29, 59, 248, 26, 97, 80, 105, 240, 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