Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a61cf8a6926369d87a27eb78f9b736078c9c5235e497815111961da3408eeeb2

Tx prefix hash: 3fb40bdc591b40e857154d1623afd30a7d2ab9ab1fe693f17a26659b6eed7f1e
Tx public key: f4a21a21972a70c35aaf16332fe1e633a5c57d96ac5338c85b0b1b082ca59fd5
Timestamp: 1708104598 Timestamp [UCT]: 2024-02-16 17:29:58 Age [y:d:h:m:s]: 01:038:21:09:35
Block: 958931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288805 RingCT/type: yes/0
Extra: 01f4a21a21972a70c35aaf16332fe1e633a5c57d96ac5338c85b0b1b082ca59fd50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3c5916e530300c42343e41a053e90eb111a140f75c03c812b6b611463853b90 0.600000000000 1418402 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": 958941, "vin": [ { "gen": { "height": 958931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3c5916e530300c42343e41a053e90eb111a140f75c03c812b6b611463853b90" } } ], "extra": [ 1, 244, 162, 26, 33, 151, 42, 112, 195, 90, 175, 22, 51, 47, 225, 230, 51, 165, 197, 125, 150, 172, 83, 56, 200, 91, 11, 27, 8, 44, 165, 159, 213, 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