Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c0e9f6f62cf545afad27d91944ca19ca71528314df01dd73394138ecf27b34d

Tx prefix hash: aa5d8aa78a9d787f1bf8a947cdcf836ed4d61a290952c1e51bf517f03d0f3d17
Tx public key: 3377cdf6a61e25bf5675c29a1373083d645c19d53e9c6c1b36d9ad0775eea0e0
Timestamp: 1707533077 Timestamp [UCT]: 2024-02-10 02:44:37 Age [y:d:h:m:s]: 01:086:20:23:34
Block: 954187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323142 RingCT/type: yes/0
Extra: 013377cdf6a61e25bf5675c29a1373083d645c19d53e9c6c1b36d9ad0775eea0e00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 643a9a838278f8b3bc9b522562afa8452c6f7436abf898716cc93e0ea7523e32 0.600000000000 1413463 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": 954197, "vin": [ { "gen": { "height": 954187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "643a9a838278f8b3bc9b522562afa8452c6f7436abf898716cc93e0ea7523e32" } } ], "extra": [ 1, 51, 119, 205, 246, 166, 30, 37, 191, 86, 117, 194, 154, 19, 115, 8, 61, 100, 92, 25, 213, 62, 156, 108, 27, 54, 217, 173, 7, 117, 238, 160, 224, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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