Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c957a9dd9d1ee2d0aa36e46f94048556607c19f0f01ce7fb4912e97d59a49e64

Tx prefix hash: c809779d593d626d997ae614adf4d821d5b52b3474c5cfc3f86843f942fa4e8d
Tx public key: 069df4da9afd54000a7d53ac00a41353c66d90464850e82ca44b4d56834b4641
Timestamp: 1686870813 Timestamp [UCT]: 2023-06-15 23:13:33 Age [y:d:h:m:s]: 01:312:09:28:47
Block: 783140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484457 RingCT/type: yes/0
Extra: 01069df4da9afd54000a7d53ac00a41353c66d90464850e82ca44b4d56834b4641021100000001faf35c9c000000000000000000

1 output(s) for total of 1.560027441000 dcy

stealth address amount amount idx
00: b68cd04bc1aa3d020c36da2743663083033bb9fe16a39e414cef8ade97f8538a 1.560027441000 1232987 of 0

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": 783150, "vin": [ { "gen": { "height": 783140 } } ], "vout": [ { "amount": 1560027441, "target": { "key": "b68cd04bc1aa3d020c36da2743663083033bb9fe16a39e414cef8ade97f8538a" } } ], "extra": [ 1, 6, 157, 244, 218, 154, 253, 84, 0, 10, 125, 83, 172, 0, 164, 19, 83, 198, 109, 144, 70, 72, 80, 232, 44, 164, 75, 77, 86, 131, 75, 70, 65, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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