Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42dd05898bc6d08818899d6a18d8d3c413a2ec6cb8d3ebf13d1383f0d637f9b1

Tx prefix hash: ec9de8730a0267aadcf745ac54723f08f8b0066c865c89584bc0995bae3587e9
Tx public key: d95b6e2f667e1a8b6550fa29d300e96268816fe7f92e712bf89e53559da111ae
Timestamp: 1684715390 Timestamp [UCT]: 2023-05-22 00:29:50 Age [y:d:h:m:s]: 01:240:08:15:32
Block: 765284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433201 RingCT/type: yes/0
Extra: 01d95b6e2f667e1a8b6550fa29d300e96268816fe7f92e712bf89e53559da111ae021100000003b3164c24000000000000000000

1 output(s) for total of 1.787708085000 dcy

stealth address amount amount idx
00: 116e74fe1dcf16f108265d59fa14e0e89dc392d0c270f5e1e0d6c0535e7c936d 1.787708085000 1214265 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": 765294, "vin": [ { "gen": { "height": 765284 } } ], "vout": [ { "amount": 1787708085, "target": { "key": "116e74fe1dcf16f108265d59fa14e0e89dc392d0c270f5e1e0d6c0535e7c936d" } } ], "extra": [ 1, 217, 91, 110, 47, 102, 126, 26, 139, 101, 80, 250, 41, 211, 0, 233, 98, 104, 129, 111, 231, 249, 46, 113, 43, 248, 158, 83, 85, 157, 161, 17, 174, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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