Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2ff0168c1250adf79ec5c85cff7e1d6ec69e1c967781be08d4d305bf8d29e4

Tx prefix hash: 443cc68fecc77d12df04dd5e3f84dfda1971b094d977ed5a5f6dc0c9291bf5ad
Tx public key: c585cb93d6bebaf1cd532898d4d1d3688638a6772769e6f76869ebd39d8e4650
Timestamp: 1714578923 Timestamp [UCT]: 2024-05-01 15:55:23 Age [y:d:h:m:s]: 00:210:13:59:24
Block: 1012614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150735 RingCT/type: yes/0
Extra: 01c585cb93d6bebaf1cd532898d4d1d3688638a6772769e6f76869ebd39d8e465002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de6eb6d71bab9a9c30434956f7c2ba801d5f07dd33802f5631ccf1b6f3ccd3f3 0.600000000000 1475198 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": 1012624, "vin": [ { "gen": { "height": 1012614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de6eb6d71bab9a9c30434956f7c2ba801d5f07dd33802f5631ccf1b6f3ccd3f3" } } ], "extra": [ 1, 197, 133, 203, 147, 214, 190, 186, 241, 205, 83, 40, 152, 212, 209, 211, 104, 134, 56, 166, 119, 39, 105, 230, 247, 104, 105, 235, 211, 157, 142, 70, 80, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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