Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf78be36316add4f0c1d099eb7bcdc1ca5fa9945c34d79e468f328558878b335

Tx prefix hash: e69156696acaa527a70dc3c2ac689dd50e2eb5834de87b57f147f1b18e58ae57
Tx public key: 2e093ab0d2afb30457bfa4e9bcf3e880600732ec51df5f6ef4a0a9d24ac8d32b
Timestamp: 1578773083 Timestamp [UCT]: 2020-01-11 20:04:43 Age [y:d:h:m:s]: 04:299:16:31:58
Block: 43404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103675 RingCT/type: yes/0
Extra: 012e093ab0d2afb30457bfa4e9bcf3e880600732ec51df5f6ef4a0a9d24ac8d32b0211000000054943cd9f000000000000000000

1 output(s) for total of 440.750558593000 dcy

stealth address amount amount idx
00: 727ac6f3a08987df5f57433ab7f1a1302ecac4f2b7ee5db675fc19a6ac7d5dff 440.750558593000 78607 of 0

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": 43414, "vin": [ { "gen": { "height": 43404 } } ], "vout": [ { "amount": 440750558593, "target": { "key": "727ac6f3a08987df5f57433ab7f1a1302ecac4f2b7ee5db675fc19a6ac7d5dff" } } ], "extra": [ 1, 46, 9, 58, 176, 210, 175, 179, 4, 87, 191, 164, 233, 188, 243, 232, 128, 96, 7, 50, 236, 81, 223, 95, 110, 244, 160, 169, 210, 74, 200, 211, 43, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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