Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b0dcac13ce587a6daac10f9b86506b663936ea6a681c5447130893b23c1bae

Tx prefix hash: 5a58fe1818dcf5a2aefb22d631261453b7f348b29e48bed825aa90d9621ce422
Tx public key: 69ee0aac365a690c50728c49e3a0e9e2da436c266e4a2276d1a6a8473e07afee
Timestamp: 1711287807 Timestamp [UCT]: 2024-03-24 13:43:27 Age [y:d:h:m:s]: 00:245:02:00:41
Block: 985345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175448 RingCT/type: yes/0
Extra: 0169ee0aac365a690c50728c49e3a0e9e2da436c266e4a2276d1a6a8473e07afee02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02feda308e74b030ed766958b2fb816308491da8f59fc2c6b0da182073df08cf 0.600000000000 1445554 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": 985355, "vin": [ { "gen": { "height": 985345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02feda308e74b030ed766958b2fb816308491da8f59fc2c6b0da182073df08cf" } } ], "extra": [ 1, 105, 238, 10, 172, 54, 90, 105, 12, 80, 114, 140, 73, 227, 160, 233, 226, 218, 67, 108, 38, 110, 74, 34, 118, 209, 166, 168, 71, 62, 7, 175, 238, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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