Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28185c1e2eb53fe77609744709a55c499ef8e3244bad4d9ef74b41d968cf484

Tx prefix hash: f0002c32bd1e64928d638fa8484299a0059c62583d08001f895bbeb805b60bb8
Tx public key: 352b7f0f2cdd3140b9e9ad65b93d6f30681cc92a5a233b8cb743bd93938baef0
Timestamp: 1677640192 Timestamp [UCT]: 2023-03-01 03:09:52 Age [y:d:h:m:s]: 02:039:10:44:42
Block: 707246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549776 RingCT/type: yes/0
Extra: 01352b7f0f2cdd3140b9e9ad65b93d6f30681cc92a5a233b8cb743bd93938baef002110000000133af99f4000000000000000000

1 output(s) for total of 2.783558243000 dcy

stealth address amount amount idx
00: e3c164c1f7f0808596aacfcd396035b7ac8506fde8600b59806d1cfee31d35f7 2.783558243000 1151043 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": 707256, "vin": [ { "gen": { "height": 707246 } } ], "vout": [ { "amount": 2783558243, "target": { "key": "e3c164c1f7f0808596aacfcd396035b7ac8506fde8600b59806d1cfee31d35f7" } } ], "extra": [ 1, 53, 43, 127, 15, 44, 221, 49, 64, 185, 233, 173, 101, 185, 61, 111, 48, 104, 28, 201, 42, 90, 35, 59, 140, 183, 67, 189, 147, 147, 139, 174, 240, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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