Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b01b455c658225dc20eaf2c1d31b64e78c8f8fb55ffcb6bfedf847711ee2c25

Tx prefix hash: 59f1040cf9b5852eadf6f5358f8f0f497c3c7621400fa2a262801d0daa153f54
Tx public key: 43857f9af46cd9a991598923b1929380be8a4e79767da11ee0de6379b8c864d3
Timestamp: 1716123152 Timestamp [UCT]: 2024-05-19 12:52:32 Age [y:d:h:m:s]: 00:279:21:11:12
Block: 1025421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200007 RingCT/type: yes/0
Extra: 0143857f9af46cd9a991598923b1929380be8a4e79767da11ee0de6379b8c864d302110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d14c0d4c09c50a57b6bc0ec3f13e09f7466b0ab06dea71c9830d67969f2fae54 0.600000000000 1491912 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": 1025431, "vin": [ { "gen": { "height": 1025421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d14c0d4c09c50a57b6bc0ec3f13e09f7466b0ab06dea71c9830d67969f2fae54" } } ], "extra": [ 1, 67, 133, 127, 154, 244, 108, 217, 169, 145, 89, 137, 35, 177, 146, 147, 128, 190, 138, 78, 121, 118, 125, 161, 30, 224, 222, 99, 121, 184, 200, 100, 211, 2, 17, 0, 0, 0, 15, 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