Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576d6e4daa218e98c52782fa92e3c748d66df08989eb89adc4a29e18da392c55

Tx prefix hash: 5a6e236d8cb7331dc117f9ee51199ae85c49a28f2ca7626bd474d0b8afb5eb05
Tx public key: a69e4d7cc882f003e6655cb43ddb91d1c5f0d0e933200f6b0034248e6012eb50
Timestamp: 1647793987 Timestamp [UCT]: 2022-03-20 16:33:07 Age [y:d:h:m:s]: 02:244:04:10:45
Block: 462650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 693975 RingCT/type: yes/0
Extra: 01a69e4d7cc882f003e6655cb43ddb91d1c5f0d0e933200f6b0034248e6012eb500211000000044a0f5013000000000000000000

1 output(s) for total of 17.990728726000 dcy

stealth address amount amount idx
00: f0a84fa903d5b5962c071ecdbbbeabd399c912573868e548de0d26ddf63e8e4c 17.990728726000 880149 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": 462660, "vin": [ { "gen": { "height": 462650 } } ], "vout": [ { "amount": 17990728726, "target": { "key": "f0a84fa903d5b5962c071ecdbbbeabd399c912573868e548de0d26ddf63e8e4c" } } ], "extra": [ 1, 166, 158, 77, 124, 200, 130, 240, 3, 230, 101, 92, 180, 61, 219, 145, 209, 197, 240, 208, 233, 51, 32, 15, 107, 0, 52, 36, 142, 96, 18, 235, 80, 2, 17, 0, 0, 0, 4, 74, 15, 80, 19, 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