Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98061f2d396aaf74761ce7aef518d81cf80b54156c138bc197992739f08a9738

Tx prefix hash: 2c6be94b3f6ae97da327c7d23bad5f71cef9d3445d0f6493392c7e59be2d0296
Tx public key: 5361c8cd7055a49df965de27ffc2dab823e1f9041630280af4f52d90fca4da8c
Timestamp: 1722125112 Timestamp [UCT]: 2024-07-28 00:05:12 Age [y:d:h:m:s]: 00:264:21:17:57
Block: 1075175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189239 RingCT/type: yes/0
Extra: 015361c8cd7055a49df965de27ffc2dab823e1f9041630280af4f52d90fca4da8c021100000017e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4c1951de1b039e8f4168e897c32d64d3d55855d795fb6ad2b60e28e9da62b12 0.600000000000 1547698 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": 1075185, "vin": [ { "gen": { "height": 1075175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4c1951de1b039e8f4168e897c32d64d3d55855d795fb6ad2b60e28e9da62b12" } } ], "extra": [ 1, 83, 97, 200, 205, 112, 85, 164, 157, 249, 101, 222, 39, 255, 194, 218, 184, 35, 225, 249, 4, 22, 48, 40, 10, 244, 245, 45, 144, 252, 164, 218, 140, 2, 17, 0, 0, 0, 23, 233, 20, 221, 21, 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