Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca2137b3f4e14a3c1abd33182b8a5745fd9c59020c81738331255aeecac13f5

Tx prefix hash: bc7f43b103ad5d4ea43448f28f73d4760509779ee33f4c74c67767e94b91aecb
Tx public key: 90339d56bde3655d1a54caa00e1c48eed0a3aed2673a6ef5eb01b88acc9629d9
Timestamp: 1709122288 Timestamp [UCT]: 2024-02-28 12:11:28 Age [y:d:h:m:s]: 01:260:04:43:34
Block: 967382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444692 RingCT/type: yes/0
Extra: 0190339d56bde3655d1a54caa00e1c48eed0a3aed2673a6ef5eb01b88acc9629d90211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38a3304bd70096279411780326c9d1b1fd2057be3160ae26359b8243bf0ed592 0.600000000000 1427159 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": 967392, "vin": [ { "gen": { "height": 967382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38a3304bd70096279411780326c9d1b1fd2057be3160ae26359b8243bf0ed592" } } ], "extra": [ 1, 144, 51, 157, 86, 189, 227, 101, 93, 26, 84, 202, 160, 14, 28, 72, 238, 208, 163, 174, 210, 103, 58, 110, 245, 235, 1, 184, 138, 204, 150, 41, 217, 2, 17, 0, 0, 0, 4, 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