Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e40a96d906bc256e72d77f540d77909d02e408d49ec1281bcb8a186155978f2e

Tx prefix hash: 5f9652ed3bb992f323572d1d409ec989094b98e3ccd189a973a29960c2e1e62f
Tx public key: 6662f036f4109791d2ee0f346bf4cfa9740591d43dc8ee9d73c3d90b9fca94d4
Timestamp: 1710585275 Timestamp [UCT]: 2024-03-16 10:34:35 Age [y:d:h:m:s]: 01:262:12:57:00
Block: 979522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446360 RingCT/type: yes/0
Extra: 016662f036f4109791d2ee0f346bf4cfa9740591d43dc8ee9d73c3d90b9fca94d40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9916ecf414fe91ceb9ff6d043e8aec8c3aa8cc2710352f0e262c7bfc2c91932 0.600000000000 1439557 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": 979532, "vin": [ { "gen": { "height": 979522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9916ecf414fe91ceb9ff6d043e8aec8c3aa8cc2710352f0e262c7bfc2c91932" } } ], "extra": [ 1, 102, 98, 240, 54, 244, 16, 151, 145, 210, 238, 15, 52, 107, 244, 207, 169, 116, 5, 145, 212, 61, 200, 238, 157, 115, 195, 217, 11, 159, 202, 148, 212, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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