Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19085f276404874e8fa80f0d660413c088a95cbcf13a8f5f139affa5c9a3d1b5

Tx prefix hash: c582b6f77eb38e748fc0961b4a71207d3c4f5c461fbff39fd13d2a354625b7a8
Tx public key: be7cc2a94fb882d0ac7cd8492970a2d1d0b738cba91a7f7ece8285da0d458dcd
Timestamp: 1708881896 Timestamp [UCT]: 2024-02-25 17:24:56 Age [y:d:h:m:s]: 01:078:13:31:28
Block: 965388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317191 RingCT/type: yes/0
Extra: 01be7cc2a94fb882d0ac7cd8492970a2d1d0b738cba91a7f7ece8285da0d458dcd02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec9eab55c15e795cd7304ed9af998c87e32c99c635b07a2c2f44b1a389b92d1b 0.600000000000 1425139 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": 965398, "vin": [ { "gen": { "height": 965388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec9eab55c15e795cd7304ed9af998c87e32c99c635b07a2c2f44b1a389b92d1b" } } ], "extra": [ 1, 190, 124, 194, 169, 79, 184, 130, 208, 172, 124, 216, 73, 41, 112, 162, 209, 208, 183, 56, 203, 169, 26, 127, 126, 206, 130, 133, 218, 13, 69, 141, 205, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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