Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864fba3226d8fdf06c810790af426368ce42e5489a05e50f7524d11962878891

Tx prefix hash: 5b2b440689f3e3c079f571c6f19146a9e13e7676d9f71052a46560b2e0a25fb3
Tx public key: d89f9c9906fa5f5ac82b9bc8f729f4a083ee6114281f48acd26d2204f5ce4bab
Timestamp: 1694066371 Timestamp [UCT]: 2023-09-07 05:59:31 Age [y:d:h:m:s]: 01:198:00:03:30
Block: 842739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402619 RingCT/type: yes/0
Extra: 01d89f9c9906fa5f5ac82b9bc8f729f4a083ee6114281f48acd26d2204f5ce4bab02110000000233af99f4000000000000000000

1 output(s) for total of 0.990047252000 dcy

stealth address amount amount idx
00: ea7c63516d7eec2fb8b0d0480db6dc27e9a72b4509dd18d12c8fd2f0c6c73b07 0.990047252000 1295889 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": 842749, "vin": [ { "gen": { "height": 842739 } } ], "vout": [ { "amount": 990047252, "target": { "key": "ea7c63516d7eec2fb8b0d0480db6dc27e9a72b4509dd18d12c8fd2f0c6c73b07" } } ], "extra": [ 1, 216, 159, 156, 153, 6, 250, 95, 90, 200, 43, 155, 200, 247, 41, 244, 160, 131, 238, 97, 20, 40, 31, 72, 172, 210, 109, 34, 4, 245, 206, 75, 171, 2, 17, 0, 0, 0, 2, 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