Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c12731d8b80439dbc1af8a610cce52636bf59cf96c62d531e1f08277ea0c4f17

Tx prefix hash: 79b39fa71a4766197c5e443997361fdeb5e228f4fd864e1d994ada5a8067702d
Tx public key: 7d360427728f9dec7b7bb993effdf91a86a51a25f26c2c9d8c3cff74e79eabe7
Timestamp: 1745131832 Timestamp [UCT]: 2025-04-20 06:50:32 Age [y:d:h:m:s]: 00:206:04:20:14
Block: 1265399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145074 RingCT/type: yes/0
Extra: 017d360427728f9dec7b7bb993effdf91a86a51a25f26c2c9d8c3cff74e79eabe7021100000001f8f51409000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30a99b24ab0975d90100b4b59fdd43941ec40246d19c007f4c93c1f12322bf8 0.600000000000 1752606 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": 1265409, "vin": [ { "gen": { "height": 1265399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30a99b24ab0975d90100b4b59fdd43941ec40246d19c007f4c93c1f12322bf8" } } ], "extra": [ 1, 125, 54, 4, 39, 114, 143, 157, 236, 123, 123, 185, 147, 239, 253, 249, 26, 134, 165, 26, 37, 242, 108, 44, 157, 140, 60, 255, 116, 231, 158, 171, 231, 2, 17, 0, 0, 0, 1, 248, 245, 20, 9, 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