Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cdc6e714dcf31b8b0fa42751d1aa429f2cd74fe023b782e1c6366a63622c2dd

Tx prefix hash: 56dc14e4da76f3af0ee3dc886854a222d3d577a86f35de768b626c01d411ca0b
Tx public key: a8ac5f7dd1f9acca900f1f830078e5abd28cb1e556caafdbe34cce1f85f06eb4
Timestamp: 1672683747 Timestamp [UCT]: 2023-01-02 18:22:27 Age [y:d:h:m:s]: 02:054:15:52:51
Block: 666144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560724 RingCT/type: yes/0
Extra: 01a8ac5f7dd1f9acca900f1f830078e5abd28cb1e556caafdbe34cce1f85f06eb40211000000045029cbac000000000000000000

1 output(s) for total of 3.808841692000 dcy

stealth address amount amount idx
00: 851d551a32e4281e76e951efcaef47db63054236da48f395f7676673478b8377 3.808841692000 1107241 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": 666154, "vin": [ { "gen": { "height": 666144 } } ], "vout": [ { "amount": 3808841692, "target": { "key": "851d551a32e4281e76e951efcaef47db63054236da48f395f7676673478b8377" } } ], "extra": [ 1, 168, 172, 95, 125, 209, 249, 172, 202, 144, 15, 31, 131, 0, 120, 229, 171, 210, 140, 177, 229, 86, 202, 175, 219, 227, 76, 206, 31, 133, 240, 110, 180, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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