Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d11f62853df1f9b117c060ebfc7797bb7d9e70fc07dea5688d7ae05200afcc2a

Tx prefix hash: 588ec567f8161ec0342aa26ff39a3bd6a7b002d63dd44955cfa2691ac85da598
Tx public key: 64dc5f759d47af308950686a0bd46cfa96871ab33279501d5f1ae5daf8d4985a
Timestamp: 1682790069 Timestamp [UCT]: 2023-04-29 17:41:09 Age [y:d:h:m:s]: 01:348:14:28:42
Block: 749312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510407 RingCT/type: yes/0
Extra: 0164dc5f759d47af308950686a0bd46cfa96871ab33279501d5f1ae5daf8d4985a021100000004e6d27f9c000000000000000000

1 output(s) for total of 2.019382061000 dcy

stealth address amount amount idx
00: 1d5f246b535abf1a86dfaa5406efc53db7f9a06b712ec39468320b3d9b9a68eb 2.019382061000 1197265 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": 749322, "vin": [ { "gen": { "height": 749312 } } ], "vout": [ { "amount": 2019382061, "target": { "key": "1d5f246b535abf1a86dfaa5406efc53db7f9a06b712ec39468320b3d9b9a68eb" } } ], "extra": [ 1, 100, 220, 95, 117, 157, 71, 175, 48, 137, 80, 104, 106, 11, 212, 108, 250, 150, 135, 26, 179, 50, 121, 80, 29, 95, 26, 229, 218, 248, 212, 152, 90, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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