Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0705b98598949392f8ae74d8b997cfa53ce54bdaefbd52c6d154202f199ec5b2

Tx prefix hash: 065ed8366bb774dd0adfb0a37f322d21c615d701df31d3f8e95bdd24cfd1b0c7
Tx public key: 0b6ff402410e8ceb6be45a29114901eb18bd79b5ea0476919fb7e089ddf5c1ee
Timestamp: 1723275148 Timestamp [UCT]: 2024-08-10 07:32:28 Age [y:d:h:m:s]: 00:213:21:12:41
Block: 1084712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152743 RingCT/type: yes/0
Extra: 010b6ff402410e8ceb6be45a29114901eb18bd79b5ea0476919fb7e089ddf5c1ee02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1016115e68448f2bc348a5f5aabd560f1d31b03c1697b9f66f6502b8639fcde6 0.600000000000 1559087 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": 1084722, "vin": [ { "gen": { "height": 1084712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1016115e68448f2bc348a5f5aabd560f1d31b03c1697b9f66f6502b8639fcde6" } } ], "extra": [ 1, 11, 111, 244, 2, 65, 14, 140, 235, 107, 228, 90, 41, 17, 73, 1, 235, 24, 189, 121, 181, 234, 4, 118, 145, 159, 183, 224, 137, 221, 245, 193, 238, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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