Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d8b20fe9cb9240a3dee32fff79fc0cd261eab9658264d77923dc231d3c18ae

Tx prefix hash: 270bf6d24c8f9b1ab0aeb11f38459d9f154a08298fadac4c0bd46cef9848a932
Tx public key: c9f34581cddfa4eae914cc451eb662c06e823ba98419e481712a77e0f7dead38
Timestamp: 1710616764 Timestamp [UCT]: 2024-03-16 19:19:24 Age [y:d:h:m:s]: 01:040:05:20:03
Block: 979779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289713 RingCT/type: yes/0
Extra: 01c9f34581cddfa4eae914cc451eb662c06e823ba98419e481712a77e0f7dead3802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 325d0e3d3779801ff5194afc7e471370484ec1aad2aa10ffb06e07b76e770ae4 0.600060000000 1439832 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": 979789, "vin": [ { "gen": { "height": 979779 } } ], "vout": [ { "amount": 600060000, "target": { "key": "325d0e3d3779801ff5194afc7e471370484ec1aad2aa10ffb06e07b76e770ae4" } } ], "extra": [ 1, 201, 243, 69, 129, 205, 223, 164, 234, 233, 20, 204, 69, 30, 182, 98, 192, 110, 130, 59, 169, 132, 25, 228, 129, 113, 42, 119, 224, 247, 222, 173, 56, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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