Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 759b58e9e1f9c39adc5af430a32ba8a5a4697758a86d91a1c60029d01916c94b

Tx prefix hash: f9a61f4518e89967b690f8f18c3f087338f827da760d3aae7eb2cddacfd05478
Tx public key: 268abf3fa522d9c2b98ae46d2f7c179ac7550732e7c5aab6b3e7537cba1f432e
Timestamp: 1708901738 Timestamp [UCT]: 2024-02-25 22:55:38 Age [y:d:h:m:s]: 01:076:14:50:55
Block: 965552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315794 RingCT/type: yes/0
Extra: 01268abf3fa522d9c2b98ae46d2f7c179ac7550732e7c5aab6b3e7537cba1f432e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0baa3eb6dcac19eb1a89602630231fc3d8eeb38fe81fbda3959fc4cbf6bcdcd7 0.600000000000 1425305 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": 965562, "vin": [ { "gen": { "height": 965552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0baa3eb6dcac19eb1a89602630231fc3d8eeb38fe81fbda3959fc4cbf6bcdcd7" } } ], "extra": [ 1, 38, 138, 191, 63, 165, 34, 217, 194, 185, 138, 228, 109, 47, 124, 23, 154, 199, 85, 7, 50, 231, 197, 170, 182, 179, 231, 83, 124, 186, 31, 67, 46, 2, 17, 0, 0, 0, 3, 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