Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd9af0a660085a236a0041d8764f7a915f55745d25bb44eb21bff330ed208d3a

Tx prefix hash: f6d7ae2211efa30434355dfe8c7245ec2f47381ccb5a18dee55c6bb96e1bec91
Tx public key: f6ae1fed325423e10a9b756412e057f98261e11ce390ce8bf99be2e1d5f877cb
Timestamp: 1709363604 Timestamp [UCT]: 2024-03-02 07:13:24 Age [y:d:h:m:s]: 00:328:11:02:09
Block: 969380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235068 RingCT/type: yes/0
Extra: 01f6ae1fed325423e10a9b756412e057f98261e11ce390ce8bf99be2e1d5f877cb02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a0494341d4d842ad5c8ba22ea778e8273b6ee5ded0891ef92e5e102965c2771 0.600000000000 1429209 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": 969390, "vin": [ { "gen": { "height": 969380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a0494341d4d842ad5c8ba22ea778e8273b6ee5ded0891ef92e5e102965c2771" } } ], "extra": [ 1, 246, 174, 31, 237, 50, 84, 35, 225, 10, 155, 117, 100, 18, 224, 87, 249, 130, 97, 225, 28, 227, 144, 206, 139, 249, 155, 226, 225, 213, 248, 119, 203, 2, 17, 0, 0, 0, 1, 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